Re: [csswg-drafts] [css-cascade-6] Add ability to scope rules from an imported stylesheet (#7348)

The CSS Working Group just discussed `[css-cascade-6] Add ability to scope rules from an imported stylesheet`, and agreed to the following:

* `RESOLVED: allow full reordering of all the current conditions on @import (MQ, scope, ...)`
* `RESOLVED: the WG recommends having an attribute to enable @scope on the HTML link element`

<details><summary>The full IRC log of that discussion</summary>
&lt;chrishtr> q+<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/7348#issuecomment-1719504814<br>
&lt;astearns> ack ydaniv<br>
&lt;fantasai> @import [ &lt;url> | &lt;string> ]<br>
&lt;fantasai>         [ layer | layer(&lt;layer-name>) ]?<br>
&lt;fantasai>         [ supports( [ &lt;supports-condition> | &lt;declaration> ] ) ]?<br>
&lt;fantasai>         &lt;media-query-list>? ;<br>
&lt;matthieud> fantasai: currently the order of trailing condition in @import is fixed<br>
&lt;astearns> ack chrishtr<br>
&lt;lea> +1 this seems pretty straightforward<br>
&lt;matthieud> fantasai:  we resolved to adding @scope on @import already<br>
&lt;lea> more generally on this issue, I wish it were possible to simply nest @import in @scope rather than need to learn new syntax<br>
&lt;astearns> ack dbaron<br>
&lt;matthieud> dbaron:  it seems that talking about reordering some of them are self explicit and media queries which are less isolated<br>
&lt;matthieud> dbaron:  we have 2 options : allow reordering everything but the MQ part ; or even across the MQ<br>
&lt;matthieud> fantasai: no strong opinion<br>
&lt;matthieud> fantasai: but no technical issue with reordering everything<br>
&lt;matthieud> astearns:  could we allow full reordering and open a following issue if there is an actual problem ?<br>
&lt;matthieud> dbaron: it's not a technical issue, but maybe it's gonna be more confusing for author<br>
&lt;matthieud> PROPOSED RESOLUTION: allow full reordering of all the current conditions on @import (MQ, scope, ...)<br>
&lt;matthieud> RESOLVED: allow full reordering of all the current conditions on @import (MQ, scope, ...)<br>
&lt;matthieud> chrishtr:  we should also add scope condition on HTML link element<br>
&lt;matthieud> miriam: the proposal is adding a scope attribute which take the scope-prelude as argument ?<br>
&lt;matthieud> fantasai: new attribute specifically for scope or a generic attribute for condition ?<br>
&lt;fantasai> s/condition/parameters<br>
&lt;matthieud> miriam:  there has been an issue in WHATWG about @layer should have its own attribute or not<br>
&lt;matthieud> miriam:  whatever the answer, we should do the same for @scope<br>
&lt;bramus> https://github.com/whatwg/html/issues/7540 is the issue<br>
&lt;matthieud> PROPOSED RESOLUTION: the WG recommends having an attribute to enable @scope on the HTML link element<br>
&lt;matthieud> RESOLVED: the WG recommends having an attribute to enable @scope on the HTML link element<br>
&lt;futhark> present-<br>
</details>


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


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

Received on Thursday, 26 September 2024 19:56:24 UTC