-
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
Changing Button
component toggled style selector
#55065
Conversation
Reverting change from class to attribute selector, until we can better assess how the `is-pressed` class is used elsewhere.
Size Change: -44 B (0%) Total Size: 1.64 MB
ℹ️ View Unchanged
|
Thanks for the PR! This change looks good to me, but I would appreciate a second review from those who worked on #54740. Note: I removed the backport label. Because #54740, which this PR is trying to solve, is not shipped in WP6.4. WP6.4 Beta2 does not have the problem that this PR is trying to solve. |
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 🚀
Tests well as per instructions
What?
This PR changes how a toggled
Button
is styled, reverting the change from class to attribute selector in #54740.Why?
It was not properly anticipated that
Button
consumers might be relying on the.is-pressed
class for styling, so until we can better assess how.is-pressed
is used elsewhere, we should leave it in place.See also #55004.
How?
This PR undoes the selector change in #54740.
Testing Instructions
This is an aesthetic change, so should make no behavioural difference. All unit tests should continue to pass.
Consuming components, including blocks, should also render as before. Any that rely on the presence of
.is-pressed
, such as the Search block toolbar, should now look as expected.To test the search block toolbar
Before
After