Re: [csswg-drafts] [css-cascade-5] Proposal to disallow interleaving of @layer and @import rules (#6522)

The CSS Working Group just discussed `disallow interweaving of @import and @layer`, and agreed to the following:

* `RESOLVED: @layer statements must occur before or after all @imports, not interleaved`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> Topic: disallow interweaving of @import and @layer<br>
&lt;TabAtkins> github:<br>
&lt;TabAtkins> miriam: xiaochang is working on a cascade layers impl, and was concerned about allowing `@layers ...;`rules allowed anywhere in the doc, including between @imports<br>
&lt;TabAtkins> miriam: He's suggesting instead we just allow them before or after all the imports, but not between<br>
&lt;TabAtkins> miriam: I think that's fine; there's no functionality loss, just a little bit of flexibility. I'm fine with this.<br>
&lt;fantasai> wfm<br>
&lt;chrishtr> +1<br>
&lt;TabAtkins> Rossen_: Seeing support, any other opinions? Objections?<br>
&lt;emilio> q+<br>
&lt;chris> ping<br>
&lt;Rossen_> ack emilio<br>
&lt;TabAtkins> emilio: I'd argue we shoudl only allow after<br>
&lt;TabAtkins> emilio: The less syntax we have to mess with preload scanners the better<br>
&lt;TabAtkins> miriam: That actually does reduce functionality, we need to be able to order layers before we import them<br>
&lt;TabAtkins> emilio: That means the scanners need to deal with this<br>
&lt;TabAtkins> emilio: Do we also allow the block syntax?<br>
&lt;TabAtkins> fantasai: No, we disallow that intentionally<br>
&lt;TabAtkins> emilio: Okay, as long as there's no arbitrary blocks before the imports it's okay<br>
&lt;Rossen_> q?<br>
&lt;TabAtkins> RESOLVED: @layer statements must occur before or after all @imports, not interleaved<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Wednesday, 25 August 2021 16:32:46 UTC