-
Notifications
You must be signed in to change notification settings - Fork 432
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
fix(core): fix issue with different Webkit tab order in forms #8022
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
No changes to documentation |
Component Testing Report Updated Dec 12, 2024 1:10 PM (UTC) ❌ Failed Tests (5) -- expand for details
|
⚡️ Editor Performance ReportUpdated Thu, 12 Dec 2024 13:11:26 GMT
Detailed information🏠 Reference resultThe performance result of
🧪 Experiment resultThe performance result of this branch
📚 Glossary
|
b871d9c
to
b8e2fa3
Compare
…o it like other browsers Chromium and Firefox will tab to the FieldActions menu without tabIndex=0, but Webkit needs to have it explicitly set in order to include it in the tab flow
b8e2fa3
to
c0695e4
Compare
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.
Thanks for this @skogsmaskin
Description
Chromium and Firefox will tab to the FieldActions menu without tabIndex=0, but Webkit needs to have it explicitly set to include it in the tab flow. Add it so all browsers follow the same tab order, and WebKit users can access the field actions with the keyboard.
This will also prevent issues with Playwright tests that rely on tabbing through forms.
What to review
That WebKit can tab into the field actions menus.
Testing
Test any form with multiple fields.
Notes for release