Joey Arhar

Ah, I didn't think of that, thanks for making that example. I think that Dan felt strongly that we should just use the flat tree to support everything that isn't...

Now that we are reusing the select element, my plan is to make the multi-select thing part of `` as well.

https://w3c.github.io/aria-practices/#combobox-keyboard-interaction says a few things about up and down: > Down Arrow: If the popup is available, moves focus into the popup: > * If the autocomplete behavior automatically selected...

I tested out the behavior on various platforms and browsers: - Up and Left choose the previous option, Down and Right choose the next option. The listbox is not opened....

We resolved to make up, down, left, and right open the listbox without changing the selected option.

We resolved to add a slot/part for this and to name it marker, and it has been implemented in the chromium prototype, so I am going to close this issue

I am implementing :open and :closed in chromium here: https://chromium-review.googlesource.com/c/chromium/src/+/4370850 I am adding :open and :closed to the selectmenu explainer here: https://github.com/openui/open-ui/pull/692

I have removed the anchor attribute from my popover HTML PR, but I am still planning on doing it as a followup. > The use case makes sense, but just...

I propose that we use the stylesheet mason linked for appearance:none. It is worth noting that we are currently developing the regular (not none) appearance and wish for that appearance...

In the current state of things, we won't get to change the styles for the select element itself since we are using the css appearance property to switch into the...