-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Make region navigation more robust #69502
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
base: trunk
Are you sure you want to change the base?
Conversation
|
Size Change: +158 B (+0.01%) Total Size: 1.84 MB
ℹ️ View Unchanged
|
|
Flaky tests detected in c44f369. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/13753512879
|
|
This might actually fix an age old bug I knew about, not sure if I reported it, but you had to tab after the page loaded before region navigation worked. I knew the region navigation exposed it's own DOM element but never thought about the fact that hooking this into the document might be better. |
What?
Enables region navigation shortcuts to work either when focus is lost or unset—the page just loaded.
Why?
Currently, region navigation may be unexpectedly disabled. The prime example is probably right when the page has loaded the shortcut should work.
How?
useNavigateRegionswith aisGlobaloption that when set totruemakes its keyboard event listeners be attached to the document instead of the element.Testing Instructions for Keyboard
Screenshots or screencast