You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
As mentioned in #11779 (comment)
The Twenty-* themes are overriding the core button styles such as .wp-block-button__link:not(.has-background). But they're doing it with an equally specific selector that also overrides the "utility" class applied for the color .has-pale-pink-background-color.
By relying on :not() to allow for color overrides, we're assuming everyone else will, as well.
Using :not() to style a button wouldn't be my first instinct.
Also discussed here #11677
To Reproduce
Steps to reproduce the behavior:
Add a button in Twenty Seventeen or Twenty Sixteen from the WP 5.0 Branch.
Color the background and text color of the button.
Check it out on the front end.
Additional context
Gutenberg v4.4
The text was updated successfully, but these errors were encountered:
This can probably be closed with the fix in #12005
But the default themes are still going to have to adjust their CSS to allow for the Button Color settings to take affect.
Describe the bug
As mentioned in #11779 (comment)
The Twenty-* themes are overriding the core button styles such as
.wp-block-button__link:not(.has-background)
. But they're doing it with an equally specific selector that also overrides the "utility" class applied for the color.has-pale-pink-background-color
.By relying on
:not()
to allow for color overrides, we're assuming everyone else will, as well.Using
:not()
to style a button wouldn't be my first instinct.Also discussed here #11677
To Reproduce
Steps to reproduce the behavior:
Additional context
The text was updated successfully, but these errors were encountered: