Global styles: block background UI controls#6836
Global styles: block background UI controls#6836ramonjd wants to merge 6 commits intoWordPress:trunkfrom
Conversation
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. |
Tests to come
output any background styles, even if there's no background image - this is so users can extend/overwrite theme.json styles
210feca to
9b4a6eb
Compare
|
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. |
aaronrobertshaw
left a comment
There was a problem hiding this comment.
Thanks for putting this together @ramonjd 👍
✅ Theme.json defined background images display in editors and frontend
✅ Code changes match GB PR
| Editor | Frontend |
|---|---|
![]() |
![]() |
I left a few minor nits as inline comments.
|
Thanks for adding the Latest changes LGTM 🚀 |
|
I appreciate the quick review! |
|
Committed in r58797. |
|
@ramonjd @joemcgill @felixarntz I ran local Server-Timing benchmarks with and without these PR changes and found that the PR is responsible for Server-Timing benchmarks
|
Interesting. Thanks for the ping! I'm at the end of my day, but I wonder if the following needs to be cached: @mukeshpanchal27 Are you comparing against local changes using https://github.com/mukeshpanchal27/compare-wp-performance? Could you share your workflow? Thanks! |
|
Good suggestion. Let's first verify that that method is indeed responsible for a notable performance decline. Maybe just comment it out and rerun the benchmarks to compare? |
Commented over here: WordPress/performance#1572 (comment) I'm not sure there's much to see here yet. I also mentioned that I think there needs to be a caching strategy for resolved URIs however:
Thank you! |


Syncing source code changes from WordPress/gutenberg#60100
Enables background images for supported blocks in global styles.
Testing
This PR adds the backend functionality only, which means the editor UI isn't yet available.
To test, define some background images for blocks. Here's an example using some of the images in
src/wp-content/themes/twentytwentyfour/{ "$schema": "../../schemas/json/theme.json", "version": 3, "settings": { "appearanceTools": true }, "styles": { "blocks": { "core/verse": { "background": { "backgroundImage": { "url": "file:./assets/images/art-gallery.webp" } } }, "core/quote": { "background": { "backgroundImage": { "url": "file:./assets/images/building-exterior.webp" } } }, "core/pullquote": { "background": { "backgroundImage": { "url": "file:./assets/images/hotel-facade.webp" } } }, "core/post-content": { "background": { "backgroundImage": { "url": "file:./assets/images/windows.webp" } } } } } }Here is some test HTML to create a test post:
The editor and frontend should display the background images:
Trac ticket: https://core.trac.wordpress.org/ticket/61588
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.