Re: [csswg-drafts] [css-cascade] When an import rule fails to load or has an unsatisfied condition, does the layer still count? (#6776)

The CSS Working Group just discussed `[css-cascade] When an import rule fails to load or has an unsatisfied condition, does the layer still count?`, and agreed to the following:

* `RESOLVED: Accept proposal`
* `RESOLVED: Republish css-cascade-5`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: [css-cascade] When an import rule fails to load or has an unsatisfied condition, does the layer still count?<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/6776<br>
&lt;fantasai> miriam: A few questions in here<br>
&lt;fantasai> miriam: All related to establishing layers inside of an @import statement.<br>
&lt;fantasai> miriam: One question is what to do if the import fails<br>
&lt;fantasai> miriam: other question is what to do if the conditions of the import don't match<br>
&lt;fantasai> miriam: consensus in the thread was that we should conceptualize this to "layer is wrapped around contents of the import, even if empty due to failure, and condition is wrapped around the whole thing"<br>
&lt;fantasai> miriam: We added language to spec to express it that way<br>
&lt;fantasai> miriam: layer is still added to layer order if import fails<br>
&lt;fantasai> miriam: but not added if the conditions don't match<br>
&lt;fantasai> miriam: that matches the behavior of if you had import inside of layer inside of condition<br>
&lt;fantasai> miriam: wanted to check with WG if this is acceptable<br>
&lt;fantasai> jensimmons: Makes a lot of sense from authoring point of view<br>
&lt;fantasai> +1 from me<br>
&lt;fantasai> RESOLVED: Accept proposal<br>
&lt;fantasai> miriam: This allows us to republish<br>
&lt;fantasai> RESOLVED: Republish css-cascade-5<br>
</details>


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


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

Received on Wednesday, 17 November 2021 17:24:36 UTC