Repository navigation
Primary button: Update disabled state to be less prominent. - #70674
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 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. |
|
Size Change: +24 B (0%) Total Size: 1.91 MB
ℹ️ View Unchanged
|
yogeshbhutkar
left a comment
There was a problem hiding this comment.
Thanks for the PR!
IMO, design-wise, the disabled state makes more sense now. However, I noticed that this doesn't work well with themes.
For Dark Theme (from storybook):

Using theme-ready variables like $components-color-gray-300 should help resolve this.
Related: #69646
|
Thanks for the review!
Nice. @ciampo do you have any insights on best next steps here? Happy to update the PR! |
|
Let's try and use the suggested variable, for the time being — and iterate later is we overehaul theming. |
0a713db to
7d31286
Compare
|
Thanks @yogeshbhutkar and Marco, I've updated with the variable and things look good!
|


What?
Related to #63856 ("Disabled states of the primary variant are very prominent, and draw a lot of attention given their un-interactivity.")
Changes the color of a disabled primary button to gray.
Why?
This makes it less prominent, and reduces confusion around the button being interactive.
Testing Instructions
Add a new post and observe the disabled "Publish" button. In this PR it shoudl be gray.
Screenshots or screencast