-
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
Fix: Templates and patterns are nesting two elements with the button role #67801
Fix: Templates and patterns are nesting two elements with the button role #67801
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Size Change: -315 B (-0.02%) Total Size: 1.83 MB
ℹ️ View Unchanged
|
Flaky tests detected in ee0409c. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/12261313073
|
Before this change, the media field of the grid layout in the Patterns screen had an extra non-interactive stop: Screen.Recording.2024-12-11.at.10.11.03.movAfter the change, it doesn't: Screen.Recording.2024-12-11.at.10.08.35.mov |
ee0409c
to
001466e
Compare
…role (WordPress#67801) Co-authored-by: jorgefilipecosta <jorgefilipecosta@git.wordpress.org> Co-authored-by: oandregal <oandregal@git.wordpress.org>
If an element has the role of button its accessibility tree can not have a button inside. Essentially that would mean we have a button inside each other.
On the template and patterns grid view, we are nesting a button inside another button for each of the grid items. This PR fixes the issue by removing the inner button. By doing that we can also remove multiple styles that are now automatically handled by data views.
Previous markup
After markup