Lena Morita

> I would like to help test this by using it on a project. However, I'm unsure what steps are involved in replacing the `@wordpress/scripts` package downloaded via npm with...

I also agree the icons are valuable. To mitigate the issue of it seeming clickable, I'm hoping we can codify this in our design guidelines for [input-like controls](https://www.figma.com/design/804HN2REV2iap2ytjRQ055/Core-System-Library?node-id=991-34623) that the...

My bad, this one doesn't contain an accessibility bug like #65340 and #65346 do.

We tried to do this once in the context of differentiating the disabled cursor state (#63816), but didn't really reach a consensus that it was a good idea. Though, I...

> To align with the css, my thinking is that `Text` and `Heading` would support predefined styles that match (or utilise, if that's possible) the scss mixins. Consumers could do...

> I was wondering if those are needed — if we allow folks to specify `variant={ undefined }`, they could just bring their own CSS, without a need for extra...

> * Contentious: `cursor: default` on resting state. Some more context [here](https://github.com/WordPress/gutenberg/issues/63756#issuecomment-2245456088), which essentially boils down to "only links should use the `pointer` cursor". I think there's a nuance here,...

How much do we take into consideration non-Latin scripts when making legibility decisions? This is what the proposed RadioControl would look like with Chinese/Japanese characters, for example: | Before |...

I went ahead and pushed a couple tweaks, if that's ok. They're mostly just architectural fixes, which shouldn't change the resulting visual. The only visual changes I added are the...

> I would be happy to discuss the newly added Setting / Styles tab at the same time. > > Perhaps it would be better to be fixed at the...