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: MaggieCabrera <onemaggie@git.wordpress.org>
Co-authored-by: jasmussen <joen@git.wordpress.org>
Co-authored-by: getdave <get_dave@git.wordpress.org>
Co-authored-by: t-hamano <wildworks@git.wordpress.org>
Co-authored-by: ocean90 <ocean90@git.wordpress.org>
Co-authored-by: mikachan <mikachan@git.wordpress.org>
Co-authored-by: carolinan <poena@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: +95 B (0%)

Total Size: 1.92 MB

_{compressed-size-action}

Please don't forget to submit a core backports PR and add a changelog entry to this PR. See https://github.com/WordPress/gutenberg/blob/trunk/backport-changelog/readme.md

Please don't forget to submit a core backports PR and add a changelog entry to this PR. See https://github.com/WordPress/gutenberg/blob/trunk/backport-changelog/readme.md

yes, it was my plan as soon as I had technical feedback on the approach, thanks for the reminder!

I need to update the description of the PR but after a long discussion with @mtias about what the best way forward we think it's best if we don't add an extra class we need to commit to maintaining in the future. Targeting the inputs directly instead is very similar to what we are already doing, if you look at the file changes of this PR, we are just moving the styles from stylesheets to theme.json, and the specificity stays the same, but we are adding the benefit of consistency between blocks (should we want to!) both core ones and third party ones. A few screenshots of my test site with and without the theme.json changes pointed in the description:

Trunk	This PR with theme.json changes	This PR with no theme.json changes

As commented on the closed PR, I am still concerned that not all text inputs needs the same styling.
For example, a text area may need to have different padding, font size, line height etc than a single line text input.

As commented on the closed PR, I am still concerned that not all text inputs needs the same styling. For example, a text area may need to have different padding, font size, line height etc than a single line text input.

I think those can still be targeted specifically, the same way it happens with heading. If you check the implementation on lib/theme.json you can see that I've done just that. The idea/goal is that we get the form block out of the experiment (when they are ready) so 3rd party blocks can just extend them, and if a specific block needs a different style, we just use the cascade.

I think elements should be an abstraction, so it wouldn't make sense to make an element specifically for the textarea, I think it's better to override the styles that don't work for it

This should be ready for review now

HEY! This is big! Kudos folks! 👏

It might be advantageaous to get this added to Gutenberg 21.6 release to testing starts two weeks earlier? What do you think @cbravobernal - it missed the RC1 by just a few hours.

it would also e great to test it together with the already merged PR for select and dropdown elements.

• Global styles: add support for select or dropdown elements #70379

It might be advantageaous to get this added to Gutenberg 21.6 release to testing starts two weeks earlier? What do you think @cbravobernal - it missed the RC1 by just a few hours.

it would also e great to test it together with the already merged PR for select and dropdown elements.

• Global styles: add support for select or dropdown elements #70379

Sure. Let's backport it.

I just cherry-picked this PR to the release/21.6 branch to get it included in the next release: 3f75e73

@MaggieCabrera what about pseudo-selectors, like :focus?

"textInput": {	
	":focus": {
		"outline": {
			"color": "red"
			"style": "solid",
			"width": "2px"
		}
	}
}

@MaggieCabrera what about pseudo-selectors, like :focus?

"textInput": {	
	":focus": {
		"outline": {
			"color": "red"
			"style": "solid",
			"width": "2px"
		}
	}
}

This would be a one liner to implement, adding this new element to the array that the button element uses to add support for pseudoselectors, but I'd wait for this recently merged PR to be tested out in the wild before adding extras to it.