Re: [csswg-drafts] [css-cascade-6] Publish an updated WD (#10370)

The CSS Working Group just discussed `[css-cascade-6] Publish an updated WD`, and agreed to the following:

* `RESOLVED: we publish current draft, and we open an issue for the multiple nested scopes`

<details><summary>The full IRC log of that discussion</summary>
&lt;matthieud> miriam:  we want to publish an updated for cascade-6 with @scope<br>
&lt;matthieud> miriam: we are not tracking multiple scope proximity, we only look at the proximity of the single closest one<br>
&lt;matthieud> miriam: do we need to resolved that first or we can publish and keeping this opened ?<br>
&lt;TabAtkins> matthieud: I think this is about taking into account nested scope, and instead of just looking at the closest one to do disambiguation..<br>
&lt;TabAtkins> matthieud: If the closest is equal in scope, you'd go up one level, etc<br>
&lt;TabAtkins> miriam: Right. Tho there's also an issue about if there's a different number of scopes.<br>
&lt;TabAtkins> matthieud: Yeah, I see no reason why it should only be the first one.<br>
&lt;TabAtkins> matthieud: Don't have giant use-cases for the nested ones, but still seems weird we completely forget about the outer scopes.<br>
&lt;matthieud> PROPOSED RESOLUTION: we publish current draft, and we open an issue for the multiple nested scopes<br>
&lt;fantasai> sgtm<br>
&lt;matthieud> RESOLVED: we publish current draft, and we open an issue for the multiple nested scopes<br>
&lt;bramus> 🎉<br>
</details>


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


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

Received on Wednesday, 21 August 2024 16:42:01 UTC