-
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
Tidying CircularOptionPicker.Option
#54903
Tidying CircularOptionPicker.Option
#54903
Conversation
Size Change: +451 B (0%) Total Size: 1.62 MB
ℹ️ View Unchanged
|
Flaky tests detected in 7fc9c02. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/6337308503
|
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.
LGTM 🚀 🚢
@andrewhayward This change brought the following side effect on tab-panel component. Steps:
|
@madhusudhand Thanks for flagging that. Sorry it was missed. Will fix. |
What?
This PR removes some now-defunct styling workarounds from
CircularOptionPicker.Option
, and normalises style application between it andButton
.Why?
Before
Button
was refactored in #54740, it was necessary to explicitly add anis-pressed
class to theCircularOptionPicker.Option
, to avoid usingisPressed
which automatically addedaria-pressed
. With those changes, and the refactor here,is-pressed
is no longer necessary as a class forCircularOptionPicker.Option
, so the workaround isn't necessary.How?
The dependency on the
is-pressed
class is removed fromCircularOptionPicker.Option
instead using thearia-selected
/aria-pressed
attribute directly.aria-selected
is also added toButton
to ensure styling is normalised for other consumers.Testing Instructions
There should be no visual changes, either in
Button
orCircularOptionPicker
. Both of these components can be checked in StoryBook.Testing Instructions for Keyboard
There should be no interaction changes to either
Button
orCircularOptionPicker
.