Repository navigation
Block Supports and design tools follow-up #76525
Copy link
Copy link
Open
Labels
[Feature] Design ToolsTools that impact the appearance of blocks both to expand the number of tools and improve the experiTools that impact the appearance of blocks both to expand the number of tools and improve the experi[Type] Tracking IssueTactical breakdown of efforts across the codebase and/or tied to Overview issues.Tactical breakdown of efforts across the codebase and/or tied to Overview issues.
Description
This issue tracks follow-up work for new and enhanced block supports and design tools, including documentation.
It follows the previous WordPress 7.0 iteration tracked in #73772.
If you're reading this, feel free to add or edit this list as supports are included or descoped.
Background supports
Text gradients and background clip
- Add text gradient and
background.backgroundClipsupport (#30982)- Refresh and complete base background clip block support infrastructure (#77141)
- Iterate on design for background clip UI (#77142)
- Final reviews, testing, and merge of background clip UI (#77142)
- Update contrast checking to be background-clipping aware to ensure text gradients causing low contrast are flagged to the user
- Show a block style variation's text colour over a block type's text gradient in Global Styles (#84599)
Background gradients
- Add
background.gradientsupport, allowing gradients and background images to be combined (#75859, #32787) - Suppress the
color.gradientcontrol whenbackground.gradientis active (#75859) - Define the compatibility and migration approach from
color.gradienttobackground.gradient - Migrate additional core blocks from
color.gradienttobackground.gradient- 71/73 blocks migrated, 1 deferred, 1 will not adopt background.gradient
Background padding
- Allow themes to control the padding applied when a block has a background color (#36586)
- Route the hardcoded padding on the seven affected blocks through the
--wp--style--block-background-paddingcustom property (#82024) -
Add a(#82057, closed)theme.jsonsetting that drives the custom property- For now themes set the custom property through custom CSS. A
theme.jsonsetting can follow if there is demand.
- For now themes set the custom property through custom CSS. A
- Route the hardcoded padding on the seven affected blocks through the
Background controls
- Consolidate background controls into the Background panel and relocate text and element color controls (#77279)
- Explore layered and ordered background controls for combinations of color, gradient, and image
- Improve interoperability and how presidence is determined for different types of background style (#83305)
- Explore allowing block supports to determine the CSS property used by the Style Engine, for example through property definitions or value functions
Dimension supports
Support foundations
- Add width and height block supports
- Add minimum width support (#76949)
- Define expected behaviour when
dimensions.widthordimensions.heightis used with:- Wide and full alignment
- Flex layouts, including grow, fit, and fixed sizing
- Grid layouts and column spans
- Blocks that apply dimensions to an inner element
- Define when dimension controls should be hidden, ignored, or translated into layout values
- Evaluate conditionally opting out of, or ignoring,
dimensions.widthwhen the parent layout is flex or grid
- Evaluate conditionally opting out of, or ignoring,
Migrate ad hoc block attributes
- Evaluate and migrate ad hoc width attributes where appropriate:
-
core/column- Column block: Migrate width to dimensions block support #76684 -
core/spacer -
core/search- Search: Migrate width to the dimensions block support #82224 -
core/comment-author-avatar -
core/image -
core/post-featured-image -
core/site-logo
-
- Evaluate and migrate ad hoc height attributes where appropriate:
-
core/comment-author-avatar -
core/image -
core/post-featured-image -
core/spacer
-
- Ensure migrations preserve existing attributes, serialized content, transforms, editor behaviour, and frontend output
Other block support follow-ups
Block support infrastructure
- Honour
background.__experimentalSkipSerializationin the editor, and adduseBackgroundPropsandgetBackgroundClassesAndStyles(#83943) - Size each fit text block in a loop on its own (#83985)
- Scope per-instance state rules to the block's root element (#83986)
- Add PHP helpers that return a block's support classes and styles, for blocks that render supports themselves (wordpress-develop#14094)
- Keep CSS colour functions such as
rgb(),oklch()andcolor-mix()in inline styles (#84213) - Remove the global border style fallbacks (#78818)
- Move the Table block's root selector to its figure, so Global Styles for links and the caption reach the caption
Position support
- Resolve sticky positioning for Template Parts (#50617)
- Coordinate with the broader position support follow-ups in #47043
Inherited Global Styles
- Display inherited Global Styles values within block inspector controls (#77894, #77595)
- Keep the current UI limited to the Gutenberg plugin while follow-up work continues (#80555)
- Complete the follow-up design and accessibility work for inherited values and local overrides
- Current iteration issue: Block Inspector: Display inherited Global Styles and local overrides (7.2) #82520
- Remove gating of displaying inherited global styles in block inspector, leaving UI behind experiment 82840
Duotone Global styles
Design tooling consistency audit
An earlier set of tracking issues audited block support adoption across the block library. Much of what they list has since landed, and the layout audit (#43248) is already closed. The rest need a pass to confirm their current state, then be closed out where they are materially complete, or have their remaining gaps folded into this issue.
- Review each audit against the current block library, close those that are materially complete, and carry any remaining gaps forward
- Implement missing block support adoptions outlined in updated (#43241)
Documentation
- Update the block supports documentation as each new support lands
- Document how theme authors control or remove the default background padding
- Document compatibility and migration guidance for block authors adopting:
-
background.backgroundClip -
background.color -
background.gradient - Dimension supports
-
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
[Feature] Design ToolsTools that impact the appearance of blocks both to expand the number of tools and improve the experiTools that impact the appearance of blocks both to expand the number of tools and improve the experi[Type] Tracking IssueTactical breakdown of efforts across the codebase and/or tied to Overview issues.Tactical breakdown of efforts across the codebase and/or tied to Overview issues.
Type
Projects
- StatusShow more project fields📋 Iteration/Tracking Issues
Activity
[-]Block Supports and design tools in WordPress 7.1[/-][+]WordPress 7.1: Block Supports and design tools[/+]annezazu commentedon Jun 16, 2026
Checking in on the iteration issue for 7.1. Is this still viable for the release? We're a month out from beta 1 and I don't see a ton of recent efforts here (which is totally fine) so I wanted to check in. If it's not slated for 7.1 but could be useful to have scoped for a future release, just remove the iteration label and remove WordPress 7.1 from the title. I'd title it something like "Block supports and design tools follow up" so it's more generic and could be reused for a future iteration issue for another release.
aaronrobertshaw commentedon Jun 22, 2026
Apologies for the slow reply here @annezazu.
A new
background.gradientblock support was added that will allow blocks to combine gradients with background images. At this stage it is still limited to the Group block however with a simple register block type filter, the block supports config for a block can be tweaked to switch over to this support if it is desired before it is adopted by further core blocks. More information can be found in:Part of the work here surfaced the need to improve the information architecture of the block inspector and global styles panels so laying those foundations has taken time away from progressing the other items in this issue.
I'll give this issue a freshen up and rename away from 7.1.
[-]WordPress 7.1: Block Supports and design tools[/-][+]Block Supports and design tools follow-up[/+]annezazu commentedon Jun 22, 2026
Thank you! Of note, I included the new block support for the Group block in the roadmap like so (that was the main piece I could find):
I'll edit to add a line about how block authors can adopt this!
aaronrobertshaw commentedon Jun 24, 2026
The relocation of color controls into the respective Typography and Background panels has been merged with #77279.
There are a few minor follow-ups that I'll take care of this week e.g. moving the contrast warning notice within the color popover etc.
The next major step will be #77894
aaronrobertshaw commentedon Aug 10, 2026
I've updated and overhauled the description in this tracking issue to be a little easier to pick up remaining tasks.
I plan to work on these in a couple of weeks time.
t-hamano commentedon Aug 12, 2026
Punting this to 7.2 as 7.1 is scheduled to be released next week.
aaronrobertshaw commentedon Sep 11, 2026
Update on the background clip support and text gradients.
Text gradients and background clip are ready for some testing and reviews. #77141 has the support, #77142 the UI, and the Core backport is wordpress-develop#13491.
On background color, the premise behind that checklist item needs correcting before anyone picks it up. It still points at #76474, which I closed, and the React error I gave as the reason there was misattributed.
The error comes from
color.gradient, which writes thebackgroundshorthand.color.backgroundalready writesbackground-color, so it is not the offender. React only complains when a shorthand and a longhand are set together, which is what happens withbackground-clip, or with a gradient and a solid color on the same block.I'll see if #77141 or #77142 can address that without the more drastic options of a new background.color support.
aaronrobertshaw commentedon Oct 2, 2026
Progress update on the block support adoption work tracked in #43241.
Since 16 September I have opened 246 pull requests across 95 blocks.
171 have merged: 63 background, 41 shadow, 26 dimensions, 17 colour, 11 typography, 8 border, 6 spacing.
73 are open and waiting on review: 23 dimensions, 12 shadow, 12 background, 9 typography and 1 fit text, 4 spacing, 3 border, 3 colour, 3 duotone, and the three fixes below.
Those three are worth looking at first, because other pull requests depend on them:
background.__experimentalSkipSerialization, so a block that applies its background to an inner element no longer disagrees with the front end. It also addsuseBackgroundPropsandgetBackgroundClassesAndStylesto@wordpress/block-editor, the helpers every other support already has. Six of the open background pull requests build on it.That leaves 177 block and support gaps. 104 of those already have a pull request open, and 73 have not been started. The biggest remaining group is width and height across the library, which I am holding until the smaller adoptions are through.
The lists in #43241 are generated from
block.jsonon trunk, so they stay mostly current as these merge.aaronrobertshaw commentedon Oct 13, 2026
Progress update for 7.2
Text gradients have landed: #77141 added the background clip support and #77142 the UI.
The Core backport is still pending wordpress-develop#13491.
Next is making the contrast checker flag text gradients with low contrast.
Block support adoption (#43241) is moving along. 71 more pull requests have merged since the last update, 242 in all. The gaps left dropped from 177 to 110, and most of those are width and height.
I've added related work to the description. That includes five PHP helpers (#84205 to #84209). They give blocks that render their own supports one place to get classes and styles.