Re: [csswg-drafts] [css-scoping] Always serialise the implicit `:scope` ? (#9621)

The CSS Working Group just discussed ``[css-scoping] Always serialise the implicit `:scope` ?``, and agreed to the following:

* `RESOLVED:  reverse the previous resolution and not serialize implicit :scope pseudos`

<details><summary>The full IRC log of that discussion</summary>
&lt;khush> andruud: if a :scope is implicitly added it's not serialized back out. because there is a diff between implicit and explicit :scope in terms of specificity<br>
&lt;khush> so they are not equivalent.<br>
&lt;khush> astearns: doesn't change anything about serialization of explicit :scope<br>
&lt;khush> astearns: proposal is to reverse the previous resolution and not serialize implicit :scope<br>
&lt;khush> matthieud: we agreed to do that for nested rules not inside ... the idea to always serialize nested rule is to take the selector from a nested rule and apply elsewhere.<br>
&lt;khush> matthieud: you can't move everything around and expect it to work automatically<br>
&lt;khush> astearns: any other comments?<br>
&lt;khush> astearns: objections to not serializing implicit scope<br>
&lt;khush> RESOLVED:  reverse the previous resolution and not serialize implicit :scope pseudos<br>
&lt;matthieud> we can' t move a relative selector like "> div" from a context where it's valid to a context where it's not valid (top level rule)<br>
&lt;khush> github-bot take up https://github.com/w3c/csswg-drafts/issues/10389<br>
</details>


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


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

Received on Wednesday, 3 July 2024 23:25:00 UTC