Add supports for states on single block instances#11452
Add supports for states on single block instances#11452MaggieCabrera wants to merge 1 commit intoWordPress:trunkfrom
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 Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Test using WordPress PlaygroundThe 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
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
| // Add the unique class to the interactive element so that state selectors | ||
| // like `.$unique_class:hover` match directly without needing a descendant. | ||
| // If the block declares selectors.root with a descendant (e.g. the button | ||
| // block's ".wp-block-button .wp-block-button__link"), we extract the last | ||
| // class and walk to that element. Otherwise we fall back to the wrapper. |
There was a problem hiding this comment.
I would go for a /* */ comment, and iirc they are recommended in the coding standards, didn't find it right now though.
Backport for WordPress/gutenberg#76491
Adds experimental support for styling blocks in different interactive states (hover, focus, active) on a per-block basis.
Trac ticket:
Use of AI Tools
This PR was authored with Claude Code (Claude Opus 4.6).
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.