You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add a default resize: vertical rule to the textarea component.
Why?
Currently within Gutenberg / the block editor, there's a default resize: vertical rule supplied by WordPress' forms.css file. So, for example, when we use the TextareaControl component within the Image block for alt text, the resize is restricted to vertical only:
However, for folks using the component outside of the block editor (or WordPress) context, this rule might not always be present. A good example is when we use DataForm's textarea control within Storybook, where the story examples for textareas can be resized horizontally, which is unexpected.
So, if we update the component to provide this default, we can ensure that consumers using textarea either via the component, or DataForm, have a more reliable default to work from.
How?
One-line code change to include a default resize: vertical rule with the TextareaControl component.
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.
Flaky tests detected in 215ad9d.
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.
The reason will be displayed to describe this comment to others. Learn more.
Oh, so it was already set in forms.css! That makes sense, because when I first noticed it was allowing horizontal resize in the Storybook, I was wondering why this never surfaced as a problem in Gutenberg 😂
More reason to deem these component styles safe to update! Thanks.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Alternative to:
Add a default
resize: vertical
rule to the textarea component.Why?
Currently within Gutenberg / the block editor, there's a default
resize: vertical
rule supplied by WordPress'forms.css
file. So, for example, when we use theTextareaControl
component within the Image block for alt text, the resize is restricted to vertical only:However, for folks using the component outside of the block editor (or WordPress) context, this rule might not always be present. A good example is when we use DataForm's textarea control within Storybook, where the story examples for textareas can be resized horizontally, which is unexpected.
So, if we update the component to provide this default, we can ensure that consumers using
textarea
either via the component, or DataForm, have a more reliable default to work from.How?
resize: vertical
rule with theTextareaControl
component.Testing Instructions
npm run storybook:dev
Screenshots or screencast
Before
2025-09-19.10.22.16.mp4
After
2025-09-19.10.22.45.mp4