-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Refactor use-tab-nav shift+tab to use existing utils #51817
Conversation
Size Change: +3.02 kB (0%) Total Size: 1.44 MB
ℹ️ View Unchanged
|
Flaky tests detected in 0fcf63e. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/5355554012
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
19dce85
to
0fcf63e
Compare
Rebasing to get the tests to pass. |
Thanks for the rebase, @scruffian! Some of the e2e tests failed due to a real bug related to passing undefined to the block utility functions. Hopefully fixed now. |
* Check for truthy values before passing to element block checks
@alexstine mentioned in the review on #51548 (review), that we could simplify the code for determining if we were inside a selected block. This PR refactors to use that code. No behaviors should be changed.
How?
Check if the element in the natural tab order of
tab
orshift+tab
is going to a tabbable elementTesting Instructions
Testing Instructions for Keyboard
Test blocks with form elements
Test Column/Group Block Tabbing (should be same as on trunk)
Test to preserve behavior from #39085
Screenshots or screencast
Screen.Recording.2023-06-15.at.11.45.27.AM.mov