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.

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: jameskoster <jameskoster@git.wordpress.org>
Co-authored-by: ciampo <mciampini@git.wordpress.org>
Co-authored-by: aduth <aduth@git.wordpress.org>

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

Size Change: +485 B (+0.02%)

Total Size: 3 MB

_{compressed-size-action}

Conventional naming — Starting scales at xs instead of 2xs follows common conventions and provides a clear and consistent "smallest" anchor.

Can you elaborate on "conventions" being followed here? It stood out to me how we now go up to 3xl (pretty big, lopsided) to achieve this, so we have xs-3xl. Wondering if a 2xs-2xl would be more "balanced". I guess part of this depends how we want specific labels to map to values, since it'd have a difference (md is12 in the former and 16 in the latter).

The more I think about it though, the more I think it's fine actually 😄 I think it's a better fit for labels to values.

Conventional naming — Starting scales at xs instead of 2xs follows common conventions and provides a clear and consistent "smallest" anchor.

Can you elaborate on "conventions" being followed here? It stood out to me how we now go up to 3xl (pretty big, lopsided) to achieve this, so we have xs-3xl. Wondering if a 2xs-2xl would be more "balanced". I guess part of this depends how we want specific labels to map to values, since it'd have a difference (md is12 in the former and 16 in the latter).

The more I think about it though, the more I think it's fine actually 😄 I think it's a better fit for labels to values.

I think it's generally fine.

IMO the important thing is that we create a scale that we can modify in the future without creating too much inconvenience for consumers:

• adding more steps at the two ends of the scale (eg 2xs, 4xl..) is going to perfectly ok;
• on the other hand, adding an extra step in the middle of the scale may be tricky

As far as we're generally confident about this (especially for the gap scale, which jumps from 16 to 24 to 40), I think we're ok

I recognise I might be slightly too deep in the weeds on this, but my thinking is that there’s some UX value in having larger scales start at the same point. If, in the majority of cases, folks can safely assume “the smallest value is xs”, that reduces a bit of cognitive overhead and makes the system feel more predictable and learnable.

As far as we're generally confident about this (especially for the gap scale, which jumps from 16 to 24 to 40), I think we're ok

It's difficult to be 100% confident without a proper vision for the admin redesign 😭 For spacing to feel intentional I think it's important to have meaningful gaps in the steps toward the larger end of the gap scale, but it might be safer to include 32 as an option.

Flaky tests detected in faa61fc.
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.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/21511538575
📝 Reported issues:

• [Flaky Test] should not be possible to edit connected blocks #74223 in /test/e2e/specs/editor/various/block-bindings/post-meta.spec.js