<select> anatomy seems Windows-centric

[othermaciej]

The proposed anatomy for a includes a part named listbox. <select> elements in macOS Safari (and in the closest matching native macOS controls) don't have a listbox, except in the <select multiple> state; they have a menu. On iPadOS, there's a popover instead. On iOS, it's a list wheel. On iOS and iPadOS, this is true even for the <select multiple> state; they use a checkable list wheel and a checkable popover respectively. I am not sure if the anatomy is meant to encompass the <select multiple> case. Can we name this part of the anatomy something that is suitable for all the different ways this control is presented on different platforms?

[dandclark]

Thanks for raising this issue!

The control anatomies that will end up being used are being developed over at WICG/open-ui, so that is the best place to raise specific anatomy issues (<select> is at https://open-ui.org/components/select). I've gone ahead and opened openui/open-ui#143 to discuss this point over there.

If OpenUI resolves to change the name or other aspects of the anatomy then I'll propagate the update to this explainer to keep it roughly in-sync with https://open-ui.org/components/select.

Meanwhile I'll also add a link to OpenUI in the standardized control UI anatomy and parts section of the explainer to call out that that's where the real anatomy will be developed, and that the sample one I've proposed in the explainer might not match the one arrived at by OpenUI and eventually standardized.

[gregwhitworth]

@othermaciej I agree that Open UI we should re-litigate the anatomy part name, that said we're doing it across all platforms, component libraries, etc - not just OS nor browser vendors. Also, the anatomy can support the scroll wheel because that is a behavior and style applied to the listbox (insert your preferred name here) but doesn't change the model nor actually the anatomy. I actually built a demo today to show tomorrow that had the list wheel but didn't have time to put in the touch items but again it's feasible given the shown window is effectively a fixed position window with the list of options in the scroll wheel.

[othermaciej]

@gregwhitworth To be clear, I think the only problem with the anatomy here is the specific name listbox, not the hierarchy. But also the anatomy does not entirely make sense for the <select multiple>/<select size=n> cases which are generally rendered as a straight listbox, with no pop-up button. I guess that ought to be a separate issue.

[gregwhitworth]

Thanks @othermaciej - ultimately I think this should be resolved over at Open UI as this isn't necessarily true:

cases which are generally rendered as a straight listbox

There are already a few issues open to explore the multiply attribute to determine the anatomy and path forward for definition from this and a11y perspective. I'll continue the discussion, and welcome your feedback, there: openui/open-ui#142

@dandclark I recommend closing this issue

[dandclark]

Closing here, let's keep discussing at openui/open-ui#142 and openui/open-ui#143.