-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
Attach to "keydown" instead of "keyup" in "/src/utils/escape-key.js" #7335
Comments
Hello. Keydown instead of keyup would not be good because it would be a change from how it is now, unexpected and imposible to cancel. But I think checking if the keydown was caught before the keyup should be ok. Please do a small test form me: replace in package.json "quasar": "^1...." with "quasar": "https://github.com/pdanpdan/quasar#quasar-v1.12.8-test.3-gitpkg" and report here if it fixes the problem. Cleanup node_modules and yarn.lock / package-lock.json and do yarn/npm install. |
Yes, your fix solves my issue. Thank you! |
Will be available in 1.12.9 |
Is your feature request related to a problem? Please describe.
I am facing the following situation (on Windows):
/src/utils/escape-key.js
- and thus the QDialog is closed without my intentionObviously this behavior is annoying.
Describe the solution you'd like
I have patched the Quasar source code (line 8 in
/src/utils/escape-key.js
) to listen forkeydown
event instead ofkeyup
- it solves my case and hopefully does not break anyone else's case.Describe alternatives you've considered
I am unable to come up with an alternative - this seems like the only possible solution.
Additional context
Screenshots will not help - but if requested, I can record a screencast (although it can not show the keyboard events and thus it seems not useful).
The text was updated successfully, but these errors were encountered: