Re: [csswg-drafts] [css-cascade-5] What happens to name-defining @-rules nested inside @layer? (#6404)

The CSS Working Group just discussed `What happens to name-defining @-rules nested inside @layer?`, and agreed to the following:

* `RESOLVED: Name-defining at-rules follow layer order for collision resolution, similar to specificity resolution.`

<details><summary>The full IRC log of that discussion</summary>
&lt;Rossen_> topic: What happens to name-defining @-rules nested inside @layer?<br>
&lt;Rossen_> github: https://github.com/w3c/csswg-drafts/issues/6404<br>
&lt;TabAtkins> miriam: Would something like @keyframes, a name-defining at-rule, work in @layer and how?<br>
&lt;TabAtkins> miriam: If there are two @keyframes with the same name, the later one wins.<br>
&lt;TabAtkins> miriam: Not common to do intentionally, but I did find some people using this to test out new animations live in production.<br>
&lt;TabAtkins> miriam: So question is if the two are defined in seaprate layers, does the layer order impact name collision reoslution?<br>
&lt;TabAtkins> miriam: I'd like to say yes, I think that's author expectation.<br>
&lt;TabAtkins> q+<br>
&lt;bkardell_> ScribeNick: bkardell_<br>
&lt;bkardell_> TabAtkins: I agree with Mia - It would rule out a lot of use cases and would be very confusing if pure source order applied to these rules<br>
&lt;bkardell_> TabAtkins: the whole point of layering is against that - I think name definiing rules should follow layer order just the same as anything else<br>
&lt;TabAtkins> ScribeNick: TabAtkins<br>
&lt;TabAtkins> Rossen_: Other opinions?<br>
&lt;TabAtkins> Rossen_: Not hearing objections, so let's resolve.<br>
&lt;TabAtkins> RESOLVED: Name-defining at-rules follow layer order for collision resolution, similar to specificity resolution.<br>
</details>


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


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

Received on Wednesday, 30 June 2021 16:35:32 UTC