- From: Mason Freed via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 Oct 2022 16:31:32 +0000
- To: public-css-archive@w3.org
> If possible, I think the mechanism we decide for `<selectmenu>` should be used for `<select>` also. The latter is also stylable (less so, but still). Using mobileness bit to decide for `<select>` and a viewport-size MQ for `<selectmenu>` seems unexpected to me. > > I don't mind switching to a MQ instead of using mobileness, if that's deemed better and is sufficiently web compatible for `<select>`. The trouble with that is that the "native" picker for `<select>` is typically only available on the "mobile" platforms. So I'm not sure what would/should happen if we're on a device where `!mobile` but `width < max-width`. Perhaps there isn't such a platform, but it seems like an odd corner case that we'd be opening up. The difference for `<selectmenu>` is that, at least by default, we weren't thinking about exposing the native picker for small screens. Perhaps there would be a CSS property that allowed the developer (or UA, if it needs to) to force the native picker, but not by default, and not triggered by the media query we're discussing. -- GitHub Notification of comment by mfreed7 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7696#issuecomment-1271805989 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 7 October 2022 16:31:34 UTC