Skip to content

Block Supports and design tools follow-up #76525

Open

Description

@aaronrobertshaw

This issue tracks follow-up work for new and enhanced block supports and design tools, including documentation. That covers polishing recently added supports, such as text gradients, and new supports, such as Transform.

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

Follow-ups from the Core backport review

These fix cases where a text gradient hides a colour or background that should show.

  • Show a block style variation's text colour over a block type's text gradient in Global Styles (#84599)
  • Undo a Global Styles or default :hover text gradient in a block's :hover and breakpoint styles (#86245)
  • Put text clip resets on blocks that style an inner element, such as the Search button (#86246)
  • Only add has-background for a background that fills the block, not one clipped to text (#86244)

Background gradients

  • Add background.gradient support, allowing gradients and background images to be combined (#75859, #32787)
  • Suppress the color.gradient control when background.gradient is active (#75859)
  • Define the compatibility and migration approach from color.gradient to background.gradient
  • Migrate additional core blocks from color.gradient to background.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-padding custom property (#82024)
    • Add a theme.json setting that drives the custom property (#82057, closed)
      • For now themes set the custom property through custom CSS. A theme.json setting can follow if there is demand.

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 precedence 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

Transform supports

A Transform block support groups visual transforms that do not affect layout, each output with its own CSS property (rotate, translate, scale), never the transform shorthand. The grid canvas work (#85505) builds on rotation, and translate will help with free placement.

  • Add the Transform block support with a rotate feature (#86240, replacing #84505)
    • Core backport: wordpress-develop#15408
    • Allow AnglePickerControl a custom range, so negative rotations are kept
    • Add rotation to :hover once an opted-in block supports that state
  • Add a translate feature, to offset a block from where layout puts it
  • Add a scale feature
  • Explore a skew feature
    • CSS has no individual skew property, so this needs a plan that avoids the transform shorthand.

Dimension supports

Support foundations

  • Add width and height block supports
  • Add minimum width support (#76949)
  • Define expected behaviour when dimensions.width or dimensions.height is 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.width when the parent layout is flex or grid

Migrate ad hoc block attributes

Other block support follow-ups

Block support infrastructure

  • Honour background.__experimentalSkipSerialization in the editor, and add useBackgroundProps and getBackgroundClassesAndStyles (#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() and color-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)
    • No longer applies. The indicator UI and its experiment were removed in #85884.
  • Complete the follow-up design and accessibility work for inherited values and local overrides
  • Remove gating of displaying inherited global styles in block inspector, leaving UI behind experiment (#82840)
  • Remove the inheritance indicators experiment, so a new origins UI can stand on its own (#85884)
  • Show a block type's current value when applying styles globally (#84823)
  • List the blocks that override an element on the Global Styles element screens (#84671)

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)
    • Adoptions landed in October 2026:
      • Icon: background image, size and gradient (#83948), minimum width and height (#83971)
      • Post Navigation Link: background image, size and gradient (#83940), minimum width and height (#83973)
      • Search: shadow (#83937), border style (#83960), minimum width and height (#83977)
      • Video: minimum width and height (#83974)
      • Table: background gradient (#83949)
      • Navigation Overlay Close: margin (#83970)
      • Tab List: line height, font weight, letter spacing and text transform (#83961)
      • Term Template: heading and button colour (#83968)
      • Comments Pagination Numbers: border (#85164)
      • Query Pagination Numbers: border and padding (#85245)
    • Finish earlier community pull requests that were picked up:

Documentation

  • Update the block supports documentation as each new support lands
  • Document how theme authors control or remove the default background padding
  • Document the Transform support for theme and block authors
  • Document compatibility and migration guidance for block authors adopting:
    • background.backgroundClip
    • background.color
    • background.gradient
    • Dimension supports

Activity

  1. added
    [Feature] Design ToolsTools that impact the appearance of blocks both to expand the number of tools and improve the experi
    [Type] IterationScoped iteration of an effort from a tracking issue or overview issue ideally for a major release.
    on Mar 16, 2026
  2. changed the title [-]Block Supports and design tools in WordPress 7.1[/-] [+]WordPress 7.1: Block Supports and design tools[/+] on Apr 16, 2026
  3. annezazu commented on Jun 16, 2026

    @annezazu
    Contributor

    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.

  4. moved this to 📋 Iteration/Tracking Issues in WordPress 7.1 Editor Taskson Jun 18, 2026
  5. aaronrobertshaw commented on Jun 22, 2026

    @aaronrobertshaw
    ContributorAuthor

    Apologies for the slow reply here @annezazu.

    A new background.gradient block 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.

  6. changed the title [-]WordPress 7.1: Block Supports and design tools[/-] [+]Block Supports and design tools follow-up[/+] on Jun 22, 2026
  7. added
    [Type] Tracking IssueTactical breakdown of efforts across the codebase and/or tied to Overview issues.
    and removed
    [Type] IterationScoped iteration of an effort from a tracking issue or overview issue ideally for a major release.
    on Jun 22, 2026
  8. annezazu commented on Jun 22, 2026

    @annezazu
    Contributor

    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):

    The Group block added support for background gradients through a new background.gradient block support, allowing gradients and background images to work together without conflicts.

    I'll edit to add a line about how block authors can adopt this!

  9. aaronrobertshaw commented on Jun 24, 2026

    @aaronrobertshaw
    ContributorAuthor

    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

  10. aaronrobertshaw commented on Aug 10, 2026

    @aaronrobertshaw
    ContributorAuthor

    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.

  11. t-hamano commented on Aug 12, 2026

    @t-hamano
    Contributor

    Punting this to 7.2 as 7.1 is scheduled to be released next week.

  12. moved this from 📋 Iteration/Tracking Issues to 🦵 Punted to 7.2 in WordPress 7.1 Editor Taskson Aug 12, 2026
  13. moved this to 📋 Iteration/Tracking Issues in WordPress 7.2 Editor Taskson Aug 13, 2026
  14. aaronrobertshaw commented on Sep 11, 2026

    @aaronrobertshaw
    ContributorAuthor

    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 the background shorthand. color.background already writes background-color, so it is not the offender. React only complains when a shorthand and a longhand are set together, which is what happens with background-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.

  15. aaronrobertshaw commented on Oct 2, 2026

    @aaronrobertshaw
    ContributorAuthor

    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:

    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.json on trunk, so they stay mostly current as these merge.

  16. aaronrobertshaw commented on Oct 13, 2026

    @aaronrobertshaw
    ContributorAuthor

    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.

    Support Merged since last update
    Dimensions 22
    Shadow 12
    Background 11
    Typography 8
    Spacing 4
    Colour 3
    Border 3
    Fixes 8

    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.

  17. aaronrobertshaw commented on Oct 30, 2026

    @aaronrobertshaw
    ContributorAuthor

    Progress update

    Since the last update:

    • #84213 keeps CSS colour functions such as rgb() and color-mix() in inline styles. The Core backport, wordpress-develop#14973, is ready for review.
    • The background clip Core backport landed in r64590.
    • #72229 added link colour to the Table block.

    For inherited Global Styles:

    • #85884 removed the indicator experiment. The inherited values in the inspector stay.
    • #84823 shows a block type's current value when applying styles globally.
    • #84671 lists the blocks that override an element on its Global Styles screen.
    • The origins UI is moving towards the "Style origins" popover in #84807. That work continues in a 7.3 iteration issue.

    The PHP helper PRs, #84205 to #84209, are being rebased and updated with review feedback.

    Next up is making the contrast checker flag text gradients with low contrast.

    I've updated the description to match.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

[Feature] Design ToolsTools 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.

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions