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: jorgefilipecosta <[email protected]>
Co-authored-by: mcsf <[email protected]>
Co-authored-by: ntsekouras <[email protected]>
Co-authored-by: ellatrix <[email protected]>
Co-authored-by: jasmussen <[email protected]>
Co-authored-by: t-hamano <[email protected]>

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

Size Change: +210 B (+0.01%)

Total Size: 2.41 MB

_{compressed-size-action}

If we go this path we will probably need better icons. cc: @jasmussen, @jameskoster would you be able to provide some icons or do you think we could use some o the existing ones?

Flaky tests detected in e28eebc.
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/19238031805
📝 Reported issues:

• [Flaky Test] All navigation links should default to the body color and submenus and mobile overlay should default to a white background with black text #55304 in /test/e2e/specs/editor/blocks/navigation-colors.spec.js

A quick iteration:

The above shows also the Paragraph LTR and RTL icons, so that the new ones can ambiguate. Those icons are also why I didn't do the potentially most obvious idea:

You can see both that it's misleading, but it also gets crowded. Thus, the ↗ style. If you like it, here are SVGs:

paragraph-stretch

<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M3 9c0 2.8 2.2 5 5 5v-.2V20h1.5V5.5H12V20h1.5V5.5h3V4H8C5.2 4 3 6.2 3 9Zm16.2-.2v1.5h2.2L17.7 14l1.1 1.1 3.7-3.7v2.2H24V8.8h-4.8Z"/></svg>

heading-stretch

<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="m3 18.6 6-4.7 6 4.7V5H3v13.6Zm16.2-9.8v1.5h2.2L17.7 14l1.1 1.1 3.7-3.7v2.2H24V8.8h-4.8Z"/></svg>

Hi @jasmussen thank you a lot for providing the icons, they were applied:

I'm here to iterate the icons if feedback suggests so: perhaps being so similar to the Paragraph isn't actually helping, and perhaps we need a single "stretch text" icon that is used for both heading and paragraph, same icon? Not clear, but let me know any feedback you hear.

One thought, though: if this is a Paragraph block variation, and we also have a Heading block variation, then the variations should be called "Stretchy Paragraph" and "Stretchy Heading", yes?

I'm here to iterate the icons if feedback suggests so: perhaps being so similar to the Paragraph isn't actually helping, and perhaps we need a single "stretch text" icon that is used for both heading and paragraph, same icon? Not clear, but let me know any feedback you hear.

One thought, though: if this is a Paragraph block variation, and we also have a Heading block variation, then the variations should be called "Stretchy Paragraph" and "Stretchy Heading", yes?

It was changed to "Stretchy Paragraph" 👍

Everyone, this PR should be backported to 6.9, right? Adding the Backport to WP 6.9 Beta/RC label to this PR will trigger an immediate cherry-pick, so I just wanted to double-check.

Update: Following this PR, I believe #73148 also needs to be backported to 6.9.

There was a conflict while trying to cherry-pick the commit to the wp/6.9 branch. Please resolve the conflict manually and create a PR to the wp/6.9 branch.

PRs to wp/6.9 are similar to PRs to trunk, but you should base your PR on the wp/6.9 branch instead of trunk.

# Checkout the wp/6.9 branch instead of trunk.
git checkout wp/6.9

# Create a new branch for your PR.
git checkout -b my-branch

# Cherry-pick the commit.
git cherry-pick 09e1eb4ec0bfb52ed2f477c64cae565b4d7c81c5

# Check which files have conflicts.
git status

# Resolve the conflict...
# Add the resolved files to the staging area.
git status
git add .
git cherry-pick --continue

# Push the branch to the repository
git push origin my-branch

# Create a PR and set the base to the wp/6.9 branch.
# See https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request.

There was a conflict while trying to cherry-pick the commit to the wp/6.9 branch. Please resolve the conflict manually and create a PR to the wp/6.9 branch.

Note: This pull request has been correctly automatically cherry-picked to the wp/6.9 branch.

8c2c469

There was a conflict while trying to cherry-pick the commit to the wp/6.9 branch. Please resolve the conflict manually and create a PR to the wp/6.9 branch.

PRs to wp/6.9 are similar to PRs to trunk, but you should base your PR on the wp/6.9 branch instead of trunk.

# Checkout the wp/6.9 branch instead of trunk.
git checkout wp/6.9

# Create a new branch for your PR.
git checkout -b my-branch

# Cherry-pick the commit.
git cherry-pick 09e1eb4ec0bfb52ed2f477c64cae565b4d7c81c5

# Check which files have conflicts.
git status

# Resolve the conflict...
# Add the resolved files to the staging area.
git status
git add .
git cherry-pick --continue

# Push the branch to the repository
git push origin my-branch

# Create a PR and set the base to the wp/6.9 branch.
# See https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request.

It was correctly cherry picked at 8c2c469 the conflict was because I made a mistake with the labels (the first seemed like the bot did not execute, but it was just a delay and then the bot tried to cherry pick a second time).

We might have to immediately comment when the action starts to signal that it's in progress.

We might have to immediately comment when the action starts to signal that it's in progress.

That would be nice 😄

@jasmussen Having just encountered those icons for the first time, I note that they only imply stretching and not shrinking. Something that implies both (example 1 / example 2) might make more sense.

perhaps we need a single "stretch text" icon that is used for both heading and paragraph

I completely agree, and would say that observation is a reason to consider reverting from the variations approach to the toggle.

We're late in the stage, I'd love in put from @youknowriad @jorgefilipecosta and others what you perceive the next steps to be.

It's always easier to add than to remove, so starting conservative is a good move. I think we should take the time to understand user feedback and act in consequence.