Joey Arhar

> But that means we cannot for instance have consistent sizing and theming for appearance:base controls, can we? That’s correct. The user agent style sheet rules will have to be...

It hadn't occurred to me before, but we could do something like `light-dark()` to support this (thanks @lilles!). We could give the UA properties that we care about an internal...

I'm not sure how to link to the definition which will be added to the HTML spec and I'm not sure how much detail we should add, I started with...

Multiple speakers at CSS day mentioned this lacking capability. I skimmed the meeting notes in this thread and it sounds like setting aria-hidden=false on a display:none element is the closest...

I also saw an article with opinions here: https://benmyers.dev/blog/native-visually-hidden/

Thanks Scott and Sara! It sounds like we should not add a CSS capability like `.visually-hidden` and perhaps should instead focus on the items in Scott's blog post: > We...

I made the spec throw exceptions due to invalid popover attribute state a while ago, but the chromium implementation still returns due to the issues mason listed here: https://github.com/whatwg/html/pull/8221#discussion_r992838111 @domenic...

> However, that raises a question: do we need two separate slots for this, or could we have a single "previously focused element" concept? Are there tests that depend on...

I forget exactly everything that was discussed at WHATNOT, but there would be risk of breakage if chrome puts user-select:none on buttons. There could be use cases where users expect...

Another side effect of my current chromium implementation is that it makes the dialog element keyboard focusable, meaning that I can focus the dialog element by pressing shift+tab when the...