Andrea Fercia

Exploring the Styles panel: Reserving the panel header to: Title and Close button. Placing additional controls within a sub-header row. That would solve many issues including providing enough space for...

> I don't think this helps clarify the UI and instead makes a worse overall design. Can you please add more context? In what way a _visible title_ for all...

> Can't we look at how to improve the toggle relationship instead without having to place things contiguously at the DOM? It is important to keep in mind that, while...

> Would a visually hidden heading work? That way it'd cover screen reader users without altering the current design, which [as I argued here](https://github.com/WordPress/gutenberg/pull/61553#issuecomment-2200005108) seems good enough as-is. @DaniGuardiola thanks...

> An idea I just though of: if headings are still helpful to some users, we could always make the "show button text labels" option into a more general "show...

> My understanding is that we are going to try this approach: #61837 > > so I'll close this PR for now. Even if #61837 would solve the Close button...

Note: for 'padding' I mean the actual visually perceived spacing. In some cases, this spacing is not determined by the actual CSS padding value, as for the 'Categories' input field...

One more place where padding inconsistency (and also sizes inconsistencies) is very evident is by comparing some block placeholders. For example: - The RSS block placeholder uses an InputControl component....

Thanks for this PR @hbhalodia. Not my area of expertise but I'd investigate why the Post Template block doesn't have the layout attribute default in the block.json in the first...

@alexstine yes those are still lowercase because it's not about the 'List VIew', as in: the tool to show and navigate the block hierarchy. Instead, those are display options of...