- From: Alexis Menard via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Apr 2025 12:05:28 +0000
- To: public-css-archive@w3.org
> It’s not about writing code against 1 segment, but about consistency when enumerating the segments. We keep saying “1 segment” but that does not rhyme with `null`. That's the thing I don't want to talk about 1 segment ever because it doesn't make sense conceptually IMHO. > > Which MQ are you talking about? AFAIK there is only the `device-posture` media feature and some env-vars that people can use. https://www.w3.org/TR/mediaqueries-5/#mf-horizontal-viewport-segments > > I asked on social media ([bsky](https://bsky.app/profile/bram.us/post/3lmkjrn2krk22), [masto](https://front-end.social/@bramus/114320482257497495)) what developers think about this: > > > 📊 Poll time: say there is an API to enumerate how many segments the viewport has. E.g. for a foldable phone the number would be 2 when the device is unfolded. > > What would you expect this API to return when the foldable is closed, or when it’s a non-foldable device? > > A. null > > B. 1 > > C. ??? > > There was an overwhelming for answer B: 1 segment. It missed context though. You should have added the semantic aspect of it. -- GitHub Notification of comment by darktears Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11957#issuecomment-2809373084 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 April 2025 12:05:29 UTC