[6.x] Increase the hit area of the breadcrumb options button - #15417
Merged
jackmcdade merged 1 commit intoSep 8, 2026
Merged
Conversation
Member
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request fixes an issue where the "Options for …" buttons render at 16x32 pixels, which is under the 24x24 minimum in WCAG 2.2 SC 2.5.8. They also sit flush against the breadcrumb link beside them, so they don't get the spacing exception either. The issue describes them as sidebar buttons, but that label only exists on the global header breadcrumb dropdown triggers and nowhere else.
The button's width was pinned to
w-4, which left 2px around the 12px chevron icon.This PR widens it to
w-6and absorbs the extra 4px on each side by bumping the negative left margin and dropping the right one, so the icon stays put and the breadcrumb layout doesn't shift.The date picker segment mentioned at the end of the issue is a reka-ui field segment rather than a button, so I've left that one for a separate PR.
Fixes #15416