- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Apr 2025 09:23:39 +0000
- To: public-css-archive@w3.org
@tabatkins Is it correct that this resolution is to extend the syntax for `@import` so that these for example becomes valid syntax: - `@import "foo.css" supports(width: 10px) or media(color);` - `@import "foo.css" media(min-width: 200px) or media(color);` If so, I am not sure if there is a use case for that 🤔 Might be interesting but wasn't really what I had in mind :) Does this allow anything that would not be possible by only adding a `media()` function that accepts a media query list? ----- Is it also correct that media types would not be allowed in `media()`? If so, does it then still solve the original issue? If CSS authors still have a reason to write bare media query lists they will still encounter the original issue, that unrelated parts might get ignored as an invalid media query. e.g. `@import "foo.css" media(color) print, something-we-havent-invented-yet;` Or do we already know that the list of types is not going to change going forwards? With `print` and `screen` being the only ones that actually have purpose. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10972#issuecomment-2778057320 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 April 2025 09:23:39 UTC