-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rendering <select> as a listbox is a one-line widget that opens a popup on iOS and Android #8189
Comments
Yeah it's unfortunate that there is a platform difference like this with the same html, and I'm worried that it's something we won't be able to change. It also poses challenges for making appearance:base work for listbox/multiple selects: https://issues.chromium.org/issues/357649033#comment4 In order to make the spec reflect the current reality, we could add some text saying that the UA may force popup rendering instead of listbox rendering if it chooses. In order to actually allow developers to have an in-page listbox rendering that is respected across platforms and that we could have appearance:base multi-select for, I wonder if we could add another attribute? |
This behavior for chromium and webkit was implmented here:
Before this patch, |
See #3410 (comment)
I suppose there's a good reason for this in terms of usability -- it may be hard to select options on a touchscreen without sufficient spacing, and taking up more space for an inline widget might be less web-compatible compared to showing a one-line widget.
On even smaller screens like a watch this approach also makes sense.
HTML doesn't currently allow it in the rendering section, however. What should the spec say? Allow either inline listbox or a one-line widget that opens a popup?
cc @whatwg/forms @mfreed7
The text was updated successfully, but these errors were encountered: