Re: [csswg-drafts] [css-cascade-6] Can we support implicit scopes in nested settings? (#10497)

The CSS Working Group just discussed `[css-cascade-6] Can we support implicit scopes in nested settings?`, and agreed to the following:

* `RESOLVED: close this issue, no change unless better arguments`

<details><summary>The full IRC log of that discussion</summary>
&lt;dbaron> ScribeNick: matthieud<br>
&lt;matthieud> miriam:  previously we creating implicit @scope root without a prelude-start<br>
&lt;matthieud> miriam:  the parent node is the implied scoping root<br>
&lt;matthieud> do we want to have the similar implicit behavior in a style rule nested context ?<br>
&lt;ydaniv> q+<br>
&lt;astearns> ack ydaniv<br>
&lt;matthieud> ydaniv:  what if it's not nested ?<br>
&lt;matthieud> miriam:  we allow non nested &amp; selector which resolve to root, could be the same<br>
&lt;astearns> ack fantasai<br>
&lt;matthieud> fantasai:  when no scope-start, it uses the closest node at the scoping root<br>
&lt;matthieud> fantasai: with this resolution, we will longer be able to reference this implicit scoping root<br>
&lt;fantasai> s/longer/no longer/<br>
&lt;matthieud> miriam:  the confusion is if you are in a style element in the doc, with an implicit @scope non nested and one nested inside a style rule, they don't have the same scoping root anymore which could be surprising<br>
&lt;ydaniv> q+<br>
&lt;fantasai> Example is<br>
&lt;matthieud> ydaniv:  it's useful to have this functionality<br>
&lt;fantasai> &lt;section>&lt;style>@scope { ... }&lt;/style>  ...&lt;/section> vs &lt;section>&lt;style>@style (&amp;) { ... }&lt;/style> ...&lt;/section.<br>
&lt;matthieud> miriam: there is no way to get back the parent node if we adopt this resolution<br>
&lt;matthieud> ydaniv: we could have a new keyword<br>
&lt;matthieud> fantasai:  there are other situation where &amp; and :scope don't represent the same element<br>
&lt;fantasai> s/fantasai/miriam/<br>
&lt;matthieud> PROPOSED SOLUTION: close this issue, no change unless better arguments<br>
&lt;matthieud> RESOLVED: close this issue, no change unless better arguments<br>
&lt;fantasai> s/better arguments/arguments for stronger than those against/<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10497#issuecomment-2377750445 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:19:51 UTC