- From: Mason Freed via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Oct 2022 16:29:37 +0000
- To: public-css-archive@w3.org
> Thanks @domenic
>
> @mfreed7 can you confirm whether `<select>` styling depends on this bit in chromium?
In Chromium, the `<select>` changes behavior based on `#ifdef ANDROID` type C++ code, which in practice should map fairly closely to the mobileness bit.
The reason I raised this issue is that for the new `<selectmenu>` element, we need to standardize the styling via CSS, including what happens on small screens. We would like behavior similar to `<select>` that gives the user a more "full screen" view when their screen size is small. It seemed natural to re-use the mobileness bit, since that's how it's done in practice for `<select>`. Without that, we'll have to have a standardized UA stylesheet that looks like this:
```css
@media screen and (max-width: 500px) {
... styling for "full screen" select ...
}
```
I anticipate endless haggling over 500px or 499px or 501px or 682px. Having said that, and given that the desire is to switch to a "small screen friendly" layout when "the screen is too small", using actual screen size does make sense. I was just hoping to side-step the bikeshedding over the pixel value. I see the points above that mobileness is kind of funny.
--
GitHub Notification of comment by mfreed7
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7696#issuecomment-1270372300 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 October 2022 16:29:38 UTC