-
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
Show borders for disabled secondary buttons. #58606
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 Core SVNIf you're a Core Committer, use this list when committing to
GitHub Merge commitsIf 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: +10 B (0%) Total Size: 1.7 MB
ℹ️ View Unchanged
|
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.
Thank you, @jasmussen!
Thanks for the green check! I'll leave this up for the weekend to see if others chime in with any observations. Mainly I want to just move slightly carefully with this one, since the Button component is so broadly used. |
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.
Looks good!
Not sure if we shared this with you but FYI, we have a matrix of Button variants in a non-public Storybook that may be useful when testing changes like this.
Run npm run storybook:e2e:dev
and see the Button ▸ Variant States story.
That is useful indeed. Thank you! Then I'll land this, it looks right, and I'll always be happy to follow up. |
What?
Secondary buttons have outlines. But not when disabled. This is causing the component to be less reliable in such sitautions, as evident by it floating a bit for the "Switch to draft" button:
This PR changes the CSS so that the secondary button always has a border, even when disabled:
Testing Instructions