You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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?
I think we first need to properly understand how we got here in the first place. Adding new features to fix an existing problem generally does not solve the problem.
Before this patch, <select multiple> and <select size=2> were always rendered in-page for all platforms. I'm guessing that there was a desire to add native support for some platforms which had multi-select popups, and it was decided to do it this way, and the platforms which didn't have native support for multi-select popups continued to use the existing in-page listbox.
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: