-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ui: New Confirmation Dialogs #7007
Conversation
81635c5
to
b89272b
Compare
d983820
to
538d113
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pulled branch locally to play with the dialog. The z-index is 👍
Yey, thanks @kaxcode ! I'm going to branch off from here to implement the new dialogs in the other areas we need them, once thats done I'll merge here and then finally merge both down to |
* ui: Implement new confirmation dialogs in other list views This includes another amend to the popover-menu in order to allow mutiple confirmations/subpanels in the same popover menu. The functionality added here to allow this is likely to change in the future.
I merged #7080 in here, everything is still passing and I tried it out some more, so I'm gonna merge this down onto |
This PR is changes our old inline confirmation dialogs to use a new style in the intention listing only (to provide context/preview).
Preview Link
Additional work on top of this will include implementing this into our other list views, currently they are completely broken so this PR should not be merged until that work is completed.
We reused our work from the namespace/dc menu here, but we've specifically disabled the keyboard navigation on these dialogs for the moment, we plan on getting this into a release before working further on the keyboard functionality here.
Also included here is a different approach to managing our z-indexing in our list views, this approach massively simplifies our previous approach and means we have to overwrite far less of the methods of the parent component.Turns out zIndexing remained problematic. But preferably we wanted to keep things simpler than the old approach, although unfortunately we still need to delve into
ember-collection
to be able to maintain correct zIndexing. The approach is simpler but hackier, but this is preferable to the old approach of duplicating all the code from theember-collection
addon. We did have a quick think as to whether we could make a child class ofGrid
so it was less hacky but as we can't control the arguments that get passed toformatItemStyle
it that wouldn't help us here. The result of all this is in d983820