-
Notifications
You must be signed in to change notification settings - Fork 0
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
[CLOSED] Handle keyboard events for nested dialogs properly #3308
Comments
|
Yup, no need to review this now. |
For comparison, here's my (very quick, possibly buggy, probably incomplete) solution: b79284afe8c615cde69e6b441d57882ea2ba641b |
|
Yeah, I like Ian's better, though I haven't looked to see if it's equivalent. |
Sunday Apr 21, 2013 at 00:49 GMT
Originally opened as adobe/brackets#3522
Instead of attaching a keydown listener for each dialog, keep track of the stack of nested dialogs and have the listener always deal with the topmost dialog. Fixes #3505.
(Ideally we wouldn't have nested dialogs at all, but the current Extension Manager implementation requires it. In the future, we might get rid of one level of dialogs there.)
Note that when #3086 (or similar) is merged, we can clean this up a bit by just having the stack hold
Dialog
objects and storingautoDismiss
in the object.As an aside, we should add some unit tests for the dialog infrastructure. Maybe the right time to do that is when we review #3086.
njx included the following code: https://github.com/adobe/brackets/pull/3522/commits
The text was updated successfully, but these errors were encountered: