Block Supports: Add background gradient support that can combine with background image by aaronrobertshaw · Pull Request #11384 · WordPress/wordpress-develop

aaronrobertshaw · 2026-03-28T07:50:54Z

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

This PR brings the PHP changes from the following Gutenberg PR to core:

Description

Adds background.gradient as a new block support, enabling blocks to combine a background gradient with a background image via comma-separated
background-image CSS values (e.g., background-image: linear-gradient(...), url(...)).

Currently, the only way to apply a gradient is through color.gradient, which renders as a background CSS shorthand and conflicts with background image
properties. By introducing background.gradient (stored at style.background.gradient), gradients become part of the background style group, allowing the
style engine to combine gradient and image values without conflict.

See: WordPress/gutenberg#32787 and WordPress/gutenberg#75859

Testing

Ensure PHP unit tests pass: npm run test:php -- --filter="Tests_Block_Supports_WpRenderBackgroundSupport|Tests_Block_Supports_Colors|Tests_wpStyleEngine|test_get_background_gradient|test_remove_insecure_p roperties_allows_combined|test_remove_insecure_properties_allows_background_gradient|test_get_settings_appearance_true"
In a theme.json file, define a background gradient for the Group block using the new styles.blocks.core/group.background.gradient property (e.g.,
"gradient": "linear-gradient(135deg, #000 0%, #fff 100%)"). Verify the gradient renders correctly on the frontend.
Also set a backgroundImage on the same Group block and confirm both values combine into a single background-image CSS declaration.
Verify existing style.color.gradient support continues to work on blocks that don't opt into background.gradient.
On a block that supports both, set both style.color.gradient and style.background.gradient — confirm background.gradient takes precedence and the
color.gradient shorthand is suppressed.

github-actions · 2026-03-28T07:51:07Z

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.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @1178653+wordpress-develop-pr-bot[bot]@users.noreply.github.com.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

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

Props aaronrobertshaw, ramonopoly, wildworks.

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

github-actions · 2026-03-28T07:56:06Z

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.

ramonjd · 2026-06-30T09:14:27Z

Sorry I've kept this waiting for so long. Just rediscovered after working on #12361

I can give it a test tomorrow - is there anything we're waiting on to get this?

aaronrobertshaw · 2026-06-30T17:31:19Z

I believe everything should be good to go with this but as it has sat for a while, I'll need to give it a rebase first

aaronrobertshaw · 2026-06-30T23:32:11Z

Actually, turns out I missed updating the core function to allow combined gradients and backgrounds properly via kses.

I've updated that now but the original Gutenberg PR only allowed modern color functions within gradients when combined with a background. I've tweaked that here so that it is consistent and they are supported for standalone gradients as well.

This will need backporting to Gutenberg so I'll spin up a PR doing that this evening or tomorrow.

ramonjd

Backport files check out against WordPress/gutenberg#75859

Test ticket annotations LGTM

I manually tested this (the latest GB release has been merged into Core already) and it's working as expected:

existing gradients and images behave
migrates existing color.gradient to background.gradient on save
image and gradient values combined in background-image

Tested theme.json in TT5 e.g.,

			"core/group": {
				"background": {
					"backgroundImage": {
						"url": "file:./assets/images/book-image-landing.webp"
					},
					"gradient": "linear-gradient(135deg,rgba(0,0,0,0.48) 1%,rgba(255,255,255,0.47) 100%)"
				}
			},

aaronrobertshaw · 2026-07-01T21:18:59Z

I've backported to Gutenberg the changes here allowing modern color definitions within standalone gradients in WordPress/gutenberg#79791

ramonjd · 2026-07-03T01:37:53Z

This one good to go you reckon?

t-hamano · 2026-07-07T10:50:12Z

I would appreciate it if you could proceed with this PR and commit it in time for the 7.1 Beta1 release on July 15.

ramonjd · 2026-07-13T00:10:11Z

@aaronrobertshaw do you need help landing this one?

ramonjd · 2026-07-13T02:43:50Z

I rebased this and retested. I think it's good to go.

… background images

… tests Add `@since 7.1.0` notes to `safecss_filter_attr()` and `wp_apply_colors_support()`, clarify the inline comment on the gradient matching in `safecss_filter_attr()`, and extend the `data_safecss_filter_attr()` provider to cover combined gradient + image values, modern colour functions, bounded nesting, and the widened single-level nested-function allowance. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

ramonjd · 2026-07-14T01:58:14Z

I'll go ahead and commit this today

ramonjd · 2026-07-14T02:17:19Z

Comitted in r62718 / 6b190c6

…g PR 79568. Assumes background gradient support from WordPress#11384. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

aaronrobertshaw · 2026-07-14T19:51:12Z

Thank you very much for picking this up and getting it committed @ramonjd 🙇

ramonjd · 2026-07-14T23:36:12Z

No worries. It's a long time coming, thanks for working on it and fixing it

aaronrobertshaw self-assigned this Mar 28, 2026

aaronrobertshaw added the enhancement label Mar 28, 2026

github-actions Bot mentioned this pull request Jun 18, 2026

PHP backports for WP 7.1 WordPress/gutenberg#79304

Closed

ramonjd mentioned this pull request Jun 30, 2026

Style Engine: Preserve important state declarations #12361

Closed

aaronrobertshaw force-pushed the add/background-gradient-support branch from af7cdca to 626797e Compare June 30, 2026 23:28

ramonjd approved these changes Jul 1, 2026

View reviewed changes

aaronrobertshaw mentioned this pull request Jul 1, 2026

Background Support: Allow modern color functions in standalone gradients WordPress/gutenberg#79791

Merged

pento force-pushed the trunk branch from 3af2d27 to 64ede28 Compare July 6, 2026 03:10

ramonjd force-pushed the add/background-gradient-support branch from f73f017 to c3100dc Compare July 13, 2026 02:28

ramonjd reviewed Jul 13, 2026

View reviewed changes

Comment thread src/wp-includes/block-supports/colors.php

ramonjd reviewed Jul 13, 2026

View reviewed changes

Comment thread src/wp-includes/kses.php Outdated

aaronrobertshaw and others added 8 commits July 14, 2026 11:36

Block Supports: Add background gradient support that can combine with…

1a7b21c

… background images

Automation: Updating built files with changes.

328e3af

Fix linting errors

8ee7148

Update core safecss_filter_attr instead of adding filter

017a490

Automation: Updating built files with changes.

1d25c46

Extend coverage for background gradient tests

991b269

since

13b9f5b

ramonjd force-pushed the add/background-gradient-support branch from f1410ad to 13b9f5b Compare July 14, 2026 01:36

ramonjd closed this Jul 14, 2026

Conversation

aaronrobertshaw commented Mar 28, 2026 • edited by ramonjd Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Testing

Uh oh!

github-actions Bot commented Mar 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Unlinked Accounts

Uh oh!

github-actions Bot commented Mar 28, 2026

Test using WordPress Playground

Some things to be aware of

Uh oh!

ramonjd commented Jun 30, 2026

Uh oh!

aaronrobertshaw commented Jun 30, 2026

Uh oh!

aaronrobertshaw commented Jun 30, 2026

Uh oh!

ramonjd left a comment

Choose a reason for hiding this comment

Uh oh!

aaronrobertshaw commented Jul 1, 2026

Uh oh!

ramonjd commented Jul 3, 2026

Uh oh!

t-hamano commented Jul 7, 2026

Uh oh!

ramonjd commented Jul 13, 2026

Uh oh!

ramonjd commented Jul 13, 2026

Uh oh!

Uh oh!

Uh oh!

ramonjd commented Jul 14, 2026

Uh oh!

ramonjd commented Jul 14, 2026

Uh oh!

aaronrobertshaw commented Jul 14, 2026

Uh oh!

ramonjd commented Jul 14, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

aaronrobertshaw commented Mar 28, 2026 •

edited by ramonjd

Loading

github-actions Bot commented Mar 28, 2026 •

edited

Loading