James Koster

@BenjaminZekavica we've begun exploring design in the [Figma](https://www.figma.com/file/8TjGue8UK7sn6qaiXdjJWK/Microsites?type=design&node-id=116%3A5594&mode=design&t=WZbNz6eziwcsWkYO-1) linked above.

For me the main question is about user expectations regarding the behavior of elements with fixed heights. Would users anticipate overflowing, clipping, or scrolling? My inclination is to implement one...

> I would lean towards hidden by default as it seems the safer starting point Agreed. I'm struggling to decide on scrolling though. For text you'd probably expect scrolling, but...

In a lot of Combobox examples I see, disabled options do tend to lighten the background as well as the text. I presume this is to create adequate visual contrast...

That example is a `menu` rather than a `combobox`, so perhaps _slightly_ different? Curiously comboboxes in ariakit don't seem to have any visual treatment for disabled options, which is a...

> having no effect, I think, makes sense for disabled options. For aria-disabled maybe it doesn't? Yes that's a good point. For sighted keyboard users it does make sense for...

> This is because it applies pointer-events: none; Oh is that necessary? I think I'd expect the hover and highlight (via keyboard) visuals to match. I'm still seeing the solid...

In the case of singular templates (single-post, page, etc) is there _ever_ a valid reason for removing this block? I'm struggling to think of one, so it might be worth...

> Locking the Content block by default would be a great start I think Agree this would be a good standard for theme authors to adopt, unsure if we should...

So long as we're happy for busy buttons to be non-interactive that might work. Though, I suppose it would have to be `aria-disabled` so that the button can retain focus?