Repository navigation
Ensure block style variations use correct selector for custom CSS on the front end - #14224
tellthemachines wants to merge 2 commits into
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. |
andrewserong
left a comment
andrewserong
left a comment
There was a problem hiding this comment.
Looks like a faithful backport to me!
Smoke-testing well on the site frontend, too:
🚢
| /** | ||
| * Tests that block style variation custom CSS, including breakpoint custom | ||
| * CSS, uses the block's css feature selector when defined. | ||
| */ |
There was a problem hiding this comment.
Should we add @ticket 66297 to this one?
There was a problem hiding this comment.
oh yes, thanks!
Trac ticket: https://core.trac.wordpress.org/ticket/66297
Use of AI Tools
used copilot with gpt-6 luna to copy changes from WordPress/gutenberg#84530. human reviewed by me.
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.