Skip to content

Fix: State styles – clear background-image when hover sets a solid background-color#12182

Open
i-am-chitti wants to merge 3 commits into
WordPress:trunkfrom
i-am-chitti:65239-state-styles-fix
Open

Fix: State styles – clear background-image when hover sets a solid background-color#12182
i-am-chitti wants to merge 3 commits into
WordPress:trunkfrom
i-am-chitti:65239-state-styles-fix

Conversation

@i-am-chitti

Copy link
Copy Markdown

Backport of WordPress/gutenberg#78992.

Description

When a block instance has a gradient applied to its default state and a solid background color applied to a pseudo-state like :hover, the hover color never appears — the gradient keeps showing despite the state styles using !important.

This is a CSS property mismatch: gradients render as background (shorthand) or background-image, while solid colors render as background-color. Since !important only resolves ties between declarations of the same property, the gradient image layer is never cleared by the hover rule.

Changes

Added wp_get_state_declarations_with_background_resets() in src/wp-includes/block-supports/states.php, called alongside the existing wp_get_state_declarations_with_fallback_border_styles().

When compiled state declarations include background-color but no background or background-image of their own, it appends background-image: unset !important to clear any gradient from the default state.

This mirrors the existing border-style fallback pattern already in the states support, and covers both:

  • Legacy color.gradient path (emits background shorthand)
  • Modern background.gradient path (emits background-image)

Trac ticket: https://core.trac.wordpress.org/ticket/65239

Use of AI Tools

No use of AI.


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

@github-actions

Copy link
Copy Markdown

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 props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props iamchitti.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions

Copy link
Copy Markdown

Hi there! 👋

Thank you for your contribution to WordPress! 💖

It looks like this is your first pull request to wordpress-develop. Here are a few things to be aware of that may help you out!

No one monitors this repository for new pull requests. Pull requests must be attached to a Trac ticket to be considered for inclusion in WordPress Core. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description.

Pull requests are never merged on GitHub. The WordPress codebase continues to be managed through the SVN repository that this GitHub repository mirrors. Please feel free to open pull requests to work on any contribution you are making.

More information about how GitHub pull requests can be used to contribute to WordPress can be found in the Core Handbook.

Please include automated tests. Including tests in your pull request is one way to help your patch be considered faster. To learn about WordPress' test suites, visit the Automated Testing page in the handbook.

If you have not had a chance, please review the Contribute with Code page in the WordPress Core Handbook.

The Developer Hub also documents the various coding standards that are followed:

Thank you,
The WordPress Project

@github-actions

Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@tellthemachines tellthemachines left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes are consistent with WordPress/gutenberg#78992.

Just a couple minor docs issues below, otherwise looks good!

* explicitly cleared. Without this, the gradient image layer remains visible
* on top of the solid hover color even when `!important` is used, because
* `background-color` and `background-image` are separate CSS properties.
*

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This function needs an @since 7.1.0 tag here (see other functions in this file for comparison).

/**
* Tests that background-image reset is added when a state sets a solid background-color.
*
* @covers ::wp_get_state_declarations_with_background_resets

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new tests should have @ticket 65239 tag (see other tests for comparison - 65239 being the trac ticket number this PR is linked with)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants