Re: [csswg-drafts] [css-conditional] Behavior of @supports(at-rule(@import)) (#11116)

The CSS Working Group just discussed `[css-conditional] Behavior of @supports(at-rule(@import))`, and agreed to the following:

* `RESOLVED: at-rule(@charset) is invalid, but at-rule(@import) is allowed`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> kbabbitt: This is about what at-rules can be tested by at-rule(), partiuclarly those with positional requirements<br>
&lt;TabAtkins> kbabbitt: anders asked about @charset and @import<br>
&lt;TabAtkins> kbabbitt: proposed resolution is @import is testable, @charset is not, because @charset isn't actually an at-rule, it just looks like one<br>
&lt;TabAtkins> kbabbitt: from Tab's epxlanation, @charset is a legacy feature that authors shoudln't be using anymore<br>
&lt;lea> q?<br>
&lt;lea> q+<br>
&lt;TabAtkins> astearns: so proposed resolution is at-rule(@charset) is not testable, but at-rule(@import) is?<br>
&lt;astearns> ack lea<br>
&lt;TabAtkins> lea: does this apply just to at-rule(), or to the larger @supports-condition thing?<br>
&lt;TabAtkins> kbabbitt: this just applies to at-rule() right now<br>
&lt;TabAtkins> astearns: objections?<br>
&lt;TabAtkins> RESOLVED: at-rule(@charset) is invalid, but at-rule(@import) is allowed<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11116#issuecomment-3205061108 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 20 August 2025 09:16:37 UTC