-
-
Notifications
You must be signed in to change notification settings - Fork 736
Add slider support for browse mode navigation #19398
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
Conversation
|
I think it's acceptable to default to not assigning gestures. |
|
Agreed with @cary-rowen here. I think it is best to leave this unassigned by default. I think there are higher priority controls that support quicknav but are still unassigned. |
|
Agreed, and there is always f/shift+f to go through all form fields or people can use the Element List. Besides that, this is a welcome change. |
|
Hi @cary-rowen, @LeonarddeR and @bramd, |
|
This feature should also be mentioned in the User Guide's chapter Other navigation commands |
|
@wmhn1872265132, done! Thanks. |
|
Could you please confirm testing and fill out the testing steps? |
|
Hi @seanbudd and @LeonarddeR, Done! Thanks. |
Link to issue number:
Fixes #17005
Summary of the issue:
Currently, slider controls (HTML range inputs and ARIA sliders) are not included in browse mode navigation. Users cannot navigate to sliders using quick navigation keys.
Description of user facing changes:
Description of developer facing changes:
Description of development approach:
Testing strategy:
Tested manually.
Known issues with pull request:
N/A
Code Review Checklist: