- From: Florian Rivoal via GitHub <noreply@w3.org>
- Date: Wed, 11 Jun 2025 02:29:26 +0000
- To: public-css-archive@w3.org
> If nobody is matching any value at all, then I'm not certain what the value is of having the MQ in the first place. (I mean, it's of pretty minimal value at this point anyway; in theory it could affect what sort of images you wanted to load, but I'd be extremely surprised if there's any pages on the web actually using it at all.) Agreed. In theory as well, matching `interlace` is also a good hint to avoid serif fonts or other very fine details, but usage cannot possibly be high. Then again, it's been around since MQ3 days, so it's had plenty of time to get exposure, so maybe there are the odd uses here and there. As for the test https://github.com/web-platform-tests/wpt/blob/master/css/mediaqueries/test_media_queries.html, expecting to matching neither `interlace` nor `progressive` would be expected under MediaQueries3 semantics (which restricted various media features to certain media they "apply to", and if you're not a TV you are supposed to match neither), but it isn't correct under Media Queries 4, which lifted these media type restrictions. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12226#issuecomment-2961040189 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 June 2025 02:29:27 UTC