Button: Remove obsolete Safari + VoiceOver workaround#77107
Conversation
|
Size Change: -61 B (0%) Total Size: 7.74 MB 📦 View Changed
ℹ️ View Unchanged
|
|
|
||
| ### Bug Fixes | ||
|
|
||
| <<<<<<< fix/rtc-inline-inserter |
|
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. |
|
Flaky tests detected in 7cc643b. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/24094770338
|
Mamaduka
left a comment
There was a problem hiding this comment.
Nice!
There is also a h5bp/main.css#12 (comment) from 2023 that the issue no longer reproduces, and I'm unable to reproduce today either, in all three major browsers.
I recently re-tested some macOS-specific a11y issues, and it seems they fixed a bunch of them. It feels great to remove similar hacks. Let's close the report as well.
What?
Removes an old Button-specific Safari + VoiceOver workaround for visually hidden text.
Why?
Originally introduced in #13221, this workaround appears to be obsolete now.
Buttonno longer renders itsVisuallyHiddendescription content inside.components-button, so the old.components-button .components-visually-hidden { height: auto; }rule no longer applies. This has been this way for at least five years, possibly more. (Note: The class name isn't set in the component file, but comes from the context system. You should indeed see it in the rendered HTML.)There is also a report from 2023 that the issue no longer reproduces, and I'm unable to reproduce today either, in all three major browsers.
Testing Instructions
npm run storybook:dev.Buttonstories.descriptionfrom the controls, and check the VoiceOver behavior.Use of AI Tools
GPT 5.4 High was used to help investigate the history of the workaround and draft this PR description.