Lena Morita

I'm afraid we're planning on moving off of Emotion, and more generally any kind of CSS-in-JS library that does any runtime work. The three main motivators being that we've been...

@youknowriad @ellatrix Any way we can make [this](https://github.com/WordPress/gutenberg/issues/61232#issuecomment-2096165432) easier for third-party component library consumers without having them rely on runtime CSS-in-JS solutions? From the current state of dev ex it...

Thank you for all your work here! I took a look at all the issues addressed in this PR, and each of them are big enough to be reviewed and...

> As for the [long strings issue](https://github.com/WordPress/gutenberg/pull/61272#issuecomment-2136367426) you summarized in the last update, this was an issue I punted from the InputBase PR (#60261) because it looked like I might...

@ciampo There are some folks in #61163 volunteering to pick this up, FWIW. @patil-vipul Are you still willing to re-submit your PR?

The breaking changes we're worrying about is around the fact that some components support an implicit controlled/uncontrolled switch through a single `value` prop (#47473). If we adopt this pattern on...

My hope is that it turns out we can do it without breaking changes though. Leave the `value` behavior as is on all components, and using the new `defaultValue` prop...

The only thing I'm concerned about is the hardcoded width. If it's ok with @WordPress/gutenberg-design, I'd like to remove the width constraints so consumers can more easily set their own...

Apologies for being late to the party, but I'm not sure how I feel about a `width` prop. It would be more straightforward for consumers to control that with a...

Just to first confirm that we're making the intended changes — do we want to expand the unit types that are available in the Typography panel only? Or expand the...