Re: [csswg-drafts] [css-cascade-5] Do conditional rules impact layer order? (#6407)

The CSS Working Group just discussed `Cascade 5`, and agreed to the following:

* `RESOLVED: If a layer is introduced in a non-global conditional rule (such as a container query), it always affects the layer order, whether or not that query matches`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: Cascade 5<br>
&lt;chris> fantasai you will do the transition request?<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/6407<br>
&lt;fantasai> miriam: Question was about defining layers defined inside global conditions like @media<br>
&lt;fantasai> miriam: but open issue about non-global condition like container queries<br>
&lt;florian> s/fantasai you will do the transition request?//<br>
&lt;fantasai> miriam: Thread concluded should always affect layer order<br>
&lt;fantasai> TabAtkins: Looks good<br>
&lt;fantasai> emilio: How do auto-conditionals behave inside container queries?<br>
&lt;fantasai> emilio: Is there a real use case for this?<br>
&lt;fantasai> miriam: If you want some of the things in the container query to be layered or not<br>
&lt;TabAtkins> fantasai: the clarification here is that there's no particular use-case for the layer existing or not conditionally, but there is a use-case for having layered styles in there, so we ahve to define it<br>
&lt;fantasai> emilio: Unfortunate to have to traverse everything<br>
&lt;fantasai> emilio: when building data structure, when finding media/supports query that doesnt' match<br>
&lt;fantasai> emilio: just skip all the rules<br>
&lt;fantasai> emilio: but here you are forced to read all the rules on the page<br>
&lt;fantasai> miriam: you have to do that anyway, because container queries aren't global, you have to read them to understand the page<br>
&lt;fantasai> TabAtkins: I think emilio misunderstood<br>
&lt;fantasai> TabAtkins: in global conditionals, they are conditional<br>
&lt;fantasai> emilio: Oh, I thought we were reverting on that. No, this makes sense.<br>
&lt;fantasai> astearns: Other comments on this?<br>
&lt;fantasai> astearns: If layer is introduced in a container query rule, it always affects layer order, whether or not that query matches anything<br>
&lt;fantasai> miriam: more broadly, any non-global condition<br>
&lt;fantasai> astearns: Any other non-globls?<br>
&lt;fantasai> miriam: Not yet<br>
&lt;fantasai> astearns: Adding that as the reason for this requirement would probably help future spec development, so add editorially<br>
&lt;fantasai> RESOLVED: If a layer is introduced in a non-global conditional rule (such as a container query), it always affects the layer order, whether or not that query matches<br>
</details>


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


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

Received on Wednesday, 14 July 2021 16:13:49 UTC