Skip to content

Block Supports: Add translate property on X and Y axis to Transform supports - #86282

Open
aaronrobertshaw wants to merge 6 commits into
add/transform-block-supportfrom
add/transform-translate
Open

aaronrobertshaw wants to merge 6 commits into
add/transform-block-supportfrom
add/transform-translate

Conversation

@aaronrobertshaw

@aaronrobertshaw aaronrobertshaw commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Important

This builds on #86240 and should merge after it.

Core backport: WordPress/wordpress-develop#15465

Related:

What?

Adds an X and Y offset to the Transform block support, via translate. Group, Heading and Video opt in.

Why?

Blocks cannot be nudged from where the layout puts them. The grid canvas in #85505 needs it too.

How?

  • Value: style.transform.translate is { x, y }, each one length or percentage.
  • Output: --wp--style--translate-x or --wp--style--translate-y for each axis set, plus translate: var(--wp--style--translate-x, 0) var(--wp--style--translate-y, 0).
  • One axis: each layer sets only its own axes, like margin sides. A block Y keeps the Global Styles X. A mobile X keeps the desktop Y.
  • No inheritance: @property with inherits: false, so nested blocks keep their own offset.
  • UI: one Offset item with a unit input and slider per axis. Only the changed axis is saved. The other shows its inherited value as a placeholder.
  • Validation: axes drop calc(), lists and a z key. KSES keeps var() in translate, as Core does elsewhere.
"styles": {
	"blocks": {
		"core/heading": {
			"transform": { "translate": { "x": "3rem" } }
		}
	}
}

Testing Instructions

Use Twenty Twenty-Five.

  1. On a Group, set X 66 and Y 35. On Mobile (Responsive styles on), set X 21. On Desktop, set Y 45. Mobile shows 21px 45px. @mobile saves only x.
  2. Add the theme.json styles above. On a Heading, X shows 3rem as a placeholder. Set Y to 1rem. Only y is saved. Both apply.
  3. Offset a Group inside an offset Group. The inner one keeps its own offset.

Screenshots or screencast

86282-offset.mp4

Use of AI Tools

Written with Claude Code, then reviewed and tested.

@aaronrobertshaw aaronrobertshaw added [Type] Enhancement A suggestion for improvement. [Feature] Design Tools Tools that impact the appearance of blocks both to expand the number of tools and improve the experi labels Nov 4, 2026
@aaronrobertshaw aaronrobertshaw self-assigned this Nov 4, 2026
@github-actions github-actions Bot added [Package] Blocks /packages/blocks [Package] Block library /packages/block-library [Package] Block editor /packages/block-editor [Package] Style Engine /packages/style-engine labels Nov 4, 2026
@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

🤖 PR meta 🤖

Preview in WordPress Playground Preview in Storybook

🎉 Props

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: aaronrobertshaw <aaronrobertshaw@git.wordpress.org>
Co-authored-by: andrewserong <andrewserong@git.wordpress.org>
Co-authored-by: tellthemachines <isabel_brison@git.wordpress.org>
Co-authored-by: jameskoster <jameskoster@git.wordpress.org>

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


Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

  • @propsbot add <username> to give props to a GitHub user. Requires write access.
  • @propsbot remove <username> to leave a user out of the props. Requires write access.
  • @propsbot refresh to refresh this list. Adding the props-bot label works too.

Updated as activity occurs, without notifying anyone named here. Add the props-bot label to refresh.

📦 Bundle size

Size Change: +1.17 kB (+0.01%)

Total Size: 8.67 MB

📦 View Changed
Filename Size Change
build/modules/lazy-editor/index.min.js 14.6 kB +4 B (+0.03%)
build/scripts/block-editor/index.min.js 556 kB +395 B (+0.07%)
build/scripts/block-library/index.min.js 427 kB +10 B (0%)
build/scripts/blocks/index.min.js 45 kB +11 B (+0.02%)
build/scripts/edit-site/index.min.js 383 kB +6 B (0%)
build/scripts/editor/index.min.js 572 kB +6 B (0%)
build/scripts/style-engine/index.min.js 2.55 kB +196 B (+8.32%) 🔍
build/styles/block-library/common-rtl.css 2.97 kB +73 B (+2.52%)
build/styles/block-library/common-rtl.min.css 1.56 kB +71 B (+4.78%) 🔍
build/styles/block-library/common.css 3 kB +71 B (+2.42%)
build/styles/block-library/common.min.css 1.55 kB +69 B (+4.65%) 🔍
build/styles/block-library/style-rtl.css 22.9 kB +67 B (+0.29%)
build/styles/block-library/style-rtl.min.css 19.5 kB +64 B (+0.33%)
build/styles/block-library/style.css 23.1 kB +65 B (+0.28%)
build/styles/block-library/style.min.css 19.5 kB +64 B (+0.33%)

031c70c Run

⚡ Performance

Show the results

Client side metrics exclude the server response time.

front-end-block-theme

Metric dcfd6ba add/transform-block-support % Change
timeToFirstByte 40.6 ms +8.5% -4.19% 35.5 ms +12.96% -6.34% 14.37%
largestContentfulPaint 68 ms +5.88% -5.88% 60 ms +13.33% -6.67% 13.33%
lcpMinusTtfb 25.2 ms +16.27% -10.71% 22.8 ms +18.42% -10.96% 10.53%
wpBeforeTemplate 20.41 ms +5.63% -4.61% 18.3 ms +13.06% -4.54% 11.53%
wpTemplate 16.27 ms +5.96% -5.59% 14.1 ms +7.09% -8.51% 15.39%
wpTotal 36.75 ms +8.76% -3.24% 32.36 ms +14.34% -6.18% 13.57%
wpMemoryUsage 7.75 MB +0% -0% 7.74 MB +0% -0% 0.13%
wpDbQueries 16 +0% -0% 16 +0% -0% 0%

front-end-classic-theme

Metric dcfd6ba add/transform-block-support % Change
timeToFirstByte 31.15 ms +8.67% -2.73% 28.9 ms +7.27% -2.08% 7.79%
largestContentfulPaint 60 ms +3.33% -6.67% 56 ms +7.14% -7.14% 7.14%
lcpMinusTtfb 27.15 ms +5.71% -4.97% 25.2 ms +8.33% -5.56% 7.74%
wpBeforeTemplate 17.1 ms +3.63% -4.09% 15.95 ms +9.84% -2.45% 7.21%
wpTemplate 11.26 ms +3.91% -3.82% 10.43 ms +5.37% -6.81% 7.96%
wpTotal 28.12 ms +7.18% -1.92% 26.35 ms +7.29% -1.9% 6.72%
wpMemoryUsage 6.44 MB +0% -0% 6.43 MB +0% -0% 0.16%
wpDbQueries 13 +0% -0% 13 +0% -0% 0%

media-processing

Metric dcfd6ba add/transform-block-support % Change
mediaProcessingJpeg 224.07 ms +3.67% -0.19% 234.07 ms +3.38% -0.19% -4.27%
mediaProcessingAvif 3717.91 ms +1.13% -0.76% 3826.11 ms +1.04% -2.36% -2.83%
mediaProcessingJpegToAvif 2606.82 ms +1.13% -1.26% 2681.81 ms +0.57% -1.19% -2.8%

media-upload

Metric dcfd6ba add/transform-block-support % Change
jpegUploadProcessing 1434.49 ms +4.16% -1.1% 1448.96 ms +0.84% -0.75% -1%
pngUploadProcessing 194.45 ms +1.35% -2.69% 195.41 ms +5.43% -6.27% -0.49%
largeJpegUploadProcessing 1454.63 ms +0.69% -1.69% 1441.47 ms +0.49% -0.52% 0.91%
multipleImageUploadProcessing 1531.5 ms +1.25% -1.54% 1488.42 ms +1.67% -0.41% 2.89%

post-editor

Metric dcfd6ba add/transform-block-support % Change
serverResponse 496.45 ms +0.54% -8.66% 467.19 ms +4.85% -5.54% 6.26%
firstPaint 450.97 ms +11.23% -7.07% 398.28 ms +13.2% -4.33% 13.23%
domContentLoaded 857.74 ms +1.53% -1.37% 821.1 ms +0.47% -2.01% 4.46%
loaded 858.85 ms +1.53% -1.37% 822.32 ms +0.45% -1.99% 4.44%
firstContentfulPaint 492.35 ms +3.17% -5.26% 462.88 ms +2.75% -3.01% 6.37%
firstBlock 2282.98 ms +8.06% -1.98% 2193.88 ms +1.77% -1.42% 4.06%
type 18.1 ms +10.5% -4.42% 18.68 ms +7.39% -7.01% -3.1%
typeWithoutInspector 18.12 ms +7.12% -11.75% 16.51 ms +12.84% -6.66% 9.75%
typeWithTopToolbar 23.42 ms +2.9% -1.88% 22.74 ms +7.7% -7.7% 2.99%
typeContainer 8.52 ms +12.32% -21.36% 8.37 ms +8.96% -14.93% 1.79%
focus 127.74 ms +9.5% -4.88% 117.04 ms +6.72% -2.07% 9.14%
firstFocus 282.53 ms +0% -0% 277.29 ms +0% -0% 1.89%
selectAll 418.31 ms +1.35% -4.56% 407.98 ms +0.92% -0.13% 2.53%
undo 30.09 ms +4.79% -6.05% 29.37 ms +4.97% -3.2% 2.45%
listViewOpen 86.64 ms +15.4% -8.38% 84.08 ms +0.87% -7.67% 3.04%
inserterOpen 45.56 ms +11.11% -9.44% 44.12 ms +13.58% -7.12% 3.26%
inserterHover 11.54 ms +14.99% -5.63% 12.23 ms +6.38% -13.16% -5.64%
inserterSearch 8.43 ms +6.41% -9.02% 8.05 ms +6.09% -7.83% 4.72%
loadPatterns 698.51 ms +6.11% -3.21% 699.12 ms +1.65% -3.22% -0.09%
wpTotal 486.43 ms +0.56% -8.8% 457.46 ms +4.94% -5.65% 6.33%
wpMemoryUsage 14.81 MB +0% -0% 14.80 MB +0% -0% 0.05%
wpDbQueries 55 +0% -0% 55 +0% -0% 0%

site-editor

Metric dcfd6ba add/transform-block-support % Change
serverResponse 468.89 ms +5.37% -4.75% 463.89 ms +3.36% -5.12% 1.08%
firstPaint 413.53 ms +14.14% -2.54% 397.09 ms +18.51% -1.31% 4.14%
domContentLoaded 866.99 ms +1.19% -1.33% 839.01 ms +0.13% -0.69% 3.33%
loaded 868.15 ms +1.22% -1.34% 839.97 ms +0.14% -0.68% 3.35%
firstContentfulPaint 482.05 ms +3.07% -1.73% 467.09 ms +0.94% -1.38% 3.2%
firstBlock 2714.49 ms +1% -0.99% 2600.69 ms +0.56% -0.56% 4.38%
type 20.1 ms +4.53% -5.82% 18.61 ms +7.15% -9.4% 8.01%
navigate 123.26 ms +3.3% -6.67% 121.64 ms +1.36% -2.92% 1.33%
loadPatterns 1422.25 ms +8.82% -3.95% 1500.7 ms +3.17% -3.97% -5.23%
loadPages 981.9 ms +2.47% -1.64% 962.5 ms +1.03% -1.36% 2.02%
wpTotal 459.33 ms +5.46% -4.9% 454.44 ms +3.38% -5.28% 1.08%
wpMemoryUsage 12.84 MB +0% -0% 12.82 MB +0% -0% 0.12%
wpDbQueries 45 +0% -0% 45 +0% -0% 0%

031c70c Run

🏁 Flaky tests

Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

Undo restores the post selection when another synced entity is loaded (RTC WebSocket) in /test/e2e/specs/editor/collaboration/collaboration-undo-redo.spec.ts, passed after 1 failed attempt.
Error: expect(received).toMatchObject(expected)

- Expected  - 2
+ Received  + 2

  Object {
    "attributeKey": "content",
    "blockIndex": 0,
    "content": "abcdef",
-   "endOffset": 3,
-   "offset": 3,
+   "endOffset": 1,
+   "offset": 1,
  }

Call Log:
- Timeout 5000ms exceeded while waiting on the predicate
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/collaboration/collaboration-undo-redo.spec.ts:363:5
does not select blocks in the canvas preview when editing from the sidebar (Site Editor v2) in /test/e2e/specs/site-editor/navigation-sidebar-list-view.spec.js, passed after 1 failed attempt.
Error: expect(locator).toBeFocused() failed

Locator: getByRole('combobox', { name: 'Search or type URL' })
Expected: focused
Timeout: 5000ms
Error: element(s) not found

Call log:
  - Expect "toBeFocused" getByRole('combobox', { name: 'Search or type URL' }) with timeout 5000ms
  - waiting for getByRole('combobox', { name: 'Search or type URL' })

    at LinkControl.useLinkControlSearch (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/navigation-sidebar-list-view.spec.js:416:47)
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/navigation-sidebar-list-view.spec.js:179:21
does not select blocks in the canvas preview when editing from the sidebar in /test/e2e/specs/site-editor/navigation-sidebar-list-view.spec.js, passed after 1 failed attempt.
Error: expect(locator).toBeVisible() failed

Locator: getByRole('listbox', { name: 'Search results' })
Expected: visible
Timeout: 5000ms
Error: element(s) not found

Call log:
  - Expect "toBeVisible" getByRole('listbox', { name: 'Search results' }) with timeout 5000ms
  - waiting for getByRole('listbox', { name: 'Search results' })

    at LinkControl.useLinkControlSearch (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/navigation-sidebar-list-view.spec.js:423:33)
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/navigation-sidebar-list-view.spec.js:179:3
should have tabs containing block examples in /test/e2e/specs/site-editor/style-book.spec.js, passed after 1 failed attempt.
Error: expect(locator).toBeVisible() failed

Locator: locator('[name="style-book-canvas"]').contentFrame().getByRole('button', { name: 'Open Image styles in Styles panel' })
Expected: visible
Error: strict mode violation: locator('[name="style-book-canvas"]') resolved to 2 elements:
    1) <iframe tabindex="0" title="Editor canvas" name="style-book-canvas" class="editor-style-book__iframe" src="blob:http://localhost:8889/b1188399-aa15-4451-9b07-b59f8c9852dc"></iframe> aka getByRole('tabpanel', { name: 'Overview' }).locator('iframe[name="style-book-canvas"]')
    2) <iframe tabindex="0" title="Editor canvas" name="style-book-canvas" class="editor-style-book__iframe" src="blob:http://localhost:8889/b1188399-aa15-4451-9b07-b59f8c9852dc"></iframe> aka getByRole('tabpanel', { name: 'Media' }).locator('iframe[name="style-book-canvas"]')

Call log:
  - Expect "toBeVisible" locator('[name="style-book-canvas"]').contentFrame().getByRole('button', { name: 'Open Image styles in Styles panel' }) with timeout 5000ms
  - waiting for locator('[name="style-book-canvas"]').contentFrame().getByRole('button', { name: 'Open Image styles in Styles panel' })

    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/style-book.spec.js:65:5
should reset a named font size using input field in /test/e2e/specs/editor/various/font-size-picker.spec.js, passed after 1 failed attempt.
Error: expect(received).toBe(expected) // Object.is equality

- Expected  - 2
+ Received  + 2

- <!-- wp:paragraph {"fontSize":"small"} -->
+ <!-- wp:paragraph {"fontSize":"tiny"} -->
- <p class="has-small-font-size">Paragraph with font size reset using input field</p>
+ <p class="has-tiny-font-size">Paragraph with font size reset using input field</p>
  <!-- /wp:paragraph -->

Call Log:
- Timeout 5000ms exceeded while waiting on the predicate
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/font-size-picker.spec.js:216:6
should select synced pattern in /test/e2e/specs/editor/various/writing-flow.spec.js, passed after 1 failed attempt.
Error: expect(locator).toBeFocused() failed

Locator:  locator('[name="editor-canvas"]').contentFrame().locator('[data-type="core/block"]')
Expected: focused
Received: inactive
Timeout:  5000ms

Call log:
  - Expect "toBeFocused" locator('[name="editor-canvas"]').contentFrame().locator('[data-type="core/block"]') with timeout 5000ms
  - waiting for locator('[name="editor-canvas"]').contentFrame().locator('[data-type="core/block"]')
    14 × locator resolved to <div tabindex="0" role="document" draggable="true" data-title="Pattern" data-type="core/block" data-is-drop-zone="true" aria-label="Block: Pattern" id="block-37c5ca16-472b-4652-957e-da703ee83c43" data-block="37c5ca16-472b-4652-957e-da703ee83c43" class="block-editor-block-list__block wp-block is-selected is-reusable block-library-block__reusable-block-container wp-block-block block-editor-block-list__layout">…</div>
       - unexpected value "inactive"

    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/writing-flow.spec.js:1464:5
shows hidden notes when adding a note in /test/e2e/specs/editor/various/block-notes-floating.spec.js, passed after 1 failed attempt.
Error: locator.click: Error: strict mode violation: getByRole('region', { name: 'Editor top bar' }).getByRole('button', { name: 'Options' }) resolved to 2 elements:
    1) <button id="_r_18_" type="button" tabindex="-1" aria-haspopup="true" aria-label="Options" aria-expanded="false" data-toolbar-item="true" class="components-button components-dropdown-menu__toggle has-icon">…</button> aka getByRole('toolbar', { name: 'Block tools' }).getByRole('button', { name: 'Options' })
    2) <button tabindex="0" type="button" id="base-ui-_r_k_" aria-haspopup="menu" aria-label="Options" aria-expanded="false" class="components-button is-compact has-icon">…</button> aka locator('#base-ui-_r_k_')

Call log:
  - waiting for getByRole('region', { name: 'Editor top bar' }).getByRole('button', { name: 'Options' })

    at BlockNoteUtils.clickNotesMenuItem (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/block-notes-utils.js:135:5)
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/block-notes-floating.spec.js:1291:25

From 0d7733a, not the current head. Run

@aaronrobertshaw aaronrobertshaw changed the title Transform: Add X and Y offsets with the translate property Block Supports: Add translate property on X and Y axis to Transform supports Nov 4, 2026
@aaronrobertshaw
aaronrobertshaw force-pushed the add/transform-block-support branch from a49cb25 to 45793e8 Compare November 9, 2026 11:34
@aaronrobertshaw
aaronrobertshaw force-pushed the add/transform-translate branch 2 times, most recently from d765b3a to 3256c31 Compare November 10, 2026 17:03
@aaronrobertshaw
aaronrobertshaw force-pushed the add/transform-block-support branch from 4584d08 to acaae5c Compare November 11, 2026 03:51
@aaronrobertshaw
aaronrobertshaw force-pushed the add/transform-block-support branch from acaae5c to 5132186 Compare November 11, 2026 07:42
@aaronrobertshaw
aaronrobertshaw force-pushed the add/transform-block-support branch from 5132186 to f2fb802 Compare November 12, 2026 03:26
@aaronrobertshaw
aaronrobertshaw marked this pull request as ready for review November 12, 2026 07:20
@aaronrobertshaw
aaronrobertshaw requested review from ramonjd and removed request for ellatrix, fabiankaegy, juanmaguitar and spacedmonkey November 12, 2026 07:20

@andrewserong andrewserong left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These PRs are really fun! One question re: the toolspanel menu — currently this splits the X and Y offsets out individually:

image

Whereas the setting for the block itself is just translate. Are we splitting them out here to make it easier to reset values individually?

While testing, it felt a tiny bit cumbersome having to click X offset and Y offset individually in order to reveal the controls. So I was wondering if it'd be worth combining them in the menu as one item (e.g. Offset or Translate) so that they're shown/hidden as a group? The side effect is that resetting would also be for the whole group, but on balance I think that might be okay?

(This is not a strongly held opinion, just observing that separate x + y menu items felt possibly a little too granular).

@tellthemachines

Copy link
Copy Markdown
Contributor

Related to the grouping X and Y axis, it looks like we need to decouple them further for viewport states. Currently, if I set some values for X and Y on desktop, and then set only a value for X on mobile, it saves the current desktop Y value under the mobile attribs too, so that if I later decide to change that value for desktop it'll persist on mobile. I think we should try to save only the explicitly set axis for viewport states.

@jameskoster

jameskoster commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

No blockers, but a couple of considerations:

  • Should users be able to choose theme spacing presets for offsets (like they do for margin and padding)?
  • Unsure how useful the sliders are, if we got rid of them the controls could be much more compact:
Screenshot 2026-11-17 at 15 07 09

Edit: I just noticed @andrewserong's comment which includes a screenshot where the inputs are arranged in a row. Disregard my comment if this was already implemented :D

@aaronrobertshaw
aaronrobertshaw force-pushed the add/transform-block-support branch from e60c57a to 78b44f8 Compare November 18, 2026 01:43
The translate feature saves an offset inline like the rotation. An offset
replaces the Global Styles offset whole, and an axis it leaves out is 0,
as in CSS. In the editor, the X and Y fields start from the inherited
values, and changing one axis saves both.

Group, Heading and Video adopt it. Transform tools, including the offset,
are switched on by appearanceTools.
Setting only the X offset on mobile now saves the block's own Y offset
with it, so mobile does not render Y as 0.
The offset tests now use Group for a block without a transform selector
and Button for a block with one, so they do not depend on the Image
block. The sanitize test uses Heading, as it already has a Group case.
@tellthemachines

Copy link
Copy Markdown
Contributor

I'm still able to repro the issue with X and Y axis from my comment above btw. What I'm doing (using a Group block):

  • On desktop, set X to 66px and Y to 35px.
  • On mobile, with responsive styles enabled, set X to 21px.
  • Back on desktop, set Y to 45px.

The new Y value updates on desktop, but on mobile the old 35px value is preserved. This is the block attrib markup after the changes:

<!-- wp:group {"style":{"transform":{"translate":{"y":"45px","x":"66px"}},"@mobile":{"transform":{"translate":{"x":"21px","y":"35px"}}}},"layout":{"type":"constrained"}} -->

(note that I never changed the value of Y on mobile, so I'd expect it to continue using whatever the current Desktop value is. I'd also expect there to be no explicit value for Y in the @mobile object unless I'd set it for that viewport)

Each layer now sets only the axes it has, as --wp--style--translate-x and
--wp--style--translate-y, and translate reads both with var(). The Offset
panel saves only the axis that changed and shows the other as a
placeholder. The two properties are registered with @Property so nested
blocks do not inherit an offset. kses keeps the new declarations.
@aaronrobertshaw

Copy link
Copy Markdown
Contributor Author

Thanks for testing again @tellthemachines 🙇

The cause was that translate is one CSS property holding both axes. A rule that sets only X resets Y to 0. To avoid that jump, the panel saved both axes, freezing a copy of the desktop Y into the mobile state.

Each axis now has its own custom property. The output is translate: var(--wp--style--translate-x, 0) var(--wp--style--translate-y, 0). Each layer sets only its own axes, so CSS fills in the rest like margin.

That covers block instances, states and Global Styles.

Your steps should now save only x under @mobile and render 21px 45px on mobile. The Offset control shows the inherited axis as a placeholder instead of saving it.

86282-axis

An inherited X of 3rem showed as 3 with px, because the empty field
gave UnitControl no unit. Pass the selected unit on its own so the
select matches the placeholder and a typed value saves in that unit.

This branch has not been deployed

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

Labels

[Feature] Design Tools Tools that impact the appearance of blocks both to expand the number of tools and improve the experi [Package] Block editor /packages/block-editor [Package] Block library /packages/block-library [Package] Blocks /packages/blocks [Package] Style Engine /packages/style-engine [Type] Enhancement A suggestion for improvement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants