-
-
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
Cannot tab forward on Quasar Plugin cancel button #12871
Comments
Shift-tab would do the trick. The "OK" button is set as default go-to for focus. |
Fix will be available in Quasar v2.6.3 and v1.18.8 |
I've never seen a dialog with the cancel button in the primary position. |
…ssibility/focus quasarframework#12871" This reverts commit 6efd92f.
…ssibility/focus quasarframework#12871" This reverts commit 6efd92f.
…ssibility/focus quasarframework#12871" This reverts commit 6efd92f.
…ssibility/focus quasarframework#12871" This reverts commit 6efd92f.
…ssibility/focus quasarframework#12871" This reverts commit 6efd92f.
This change needs to be a MAJOR version, this is almost a breaking change... Anyway this not looks good in a Dialog, even the Material spec says the accept button must be in rigth like @pdanpdan says: |
Working on another fix rather than switching buttons order, but in the meantime we can't leave out important functionality. |
…t time; then on focusing out it should look for any focusable element; also revert DialogPlugin button order #12871
…ofocusable only first time; then on focusing out it should look for any focusable element; also revert DialogPlugin button order #12871
What happened?
when tabbing continuously in the Dialog, it will not focus in the cancel button.
What did you expect to happen?
It should be able to focus
Reproduction URL
https://codepen.io/gwynncausing/pen/popNjpX
How to reproduce?
Flavour
Quasar CLI (@quasar/cli | @quasar/app)
Areas
Components (quasar), Plugins (quasar)
Platforms/Browsers
Chrome, Microsoft Edge
Quasar info output
No response
Relevant log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: