Joey Arhar

To reiterate, here are the modes I am proposing supporting: 1. single-select with a **custom button** and a **custom popup listbox** ```html custom button ... ``` 2. single-select with a...

> I don't think "native" vs "custom" should follow from markup. It should follow from CSS. There might well be limits to a "native" appearance, forcing a user agent to...

> I could see offering a replacement for size, maybe, but multiple is the API across several controls for multiple values. Sounds good to me. Greg's suggestion of creating a...

Since we are committed to doing a CSS solution for the customizable select project, the answer here is simple: `` and `` will not support appearance:base/base-select for the initial launch...

So we shouldn't do typeahead while the listbox is closed? Seems fine to me I guess. I suppose some people might like this behavior, but i shouldn't be too hard...

Yeah I feel that we should do something since typeahead when the listbox is closed seems to work on all platforms for the existing `` element

> I could imagine adding a mechanism to anchor positioning that allowed applying the transform taken from an anchor to the anchor-positioned element. In the sentiment of this comment, I...

I think this should be solved by anchor positioning rather than being a select-specific behavior we add for appearance:base. I'll post about it in the crbug

> masonf: agreed to move forward with some sort of placeholder, tentative to use parts and slots, any objection to move along that route? So it sounds like we should...

The existing `` element supports clearing the selected value by doing `element.value = ''` or `element.value = null`. I think this is something we could easily copy for selectmenu. As...