Re: [csswg-drafts] [css-scoping] [selectors] <compound-selector-list> should somehow affect :is() / :where() parsing (#5093)

The CSS Working Group just discussed `[css-scoping] [selectors] <compound-selector-list> should somehow affect :is() / :where() parsing`, and agreed to the following:

* `RESOLVED: Accept the edit`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> TabAtkins: Summary is after some discussion across a few related issues, basic idea is logical combo pseudos that combine things together passes down any restrictions the outer pseudo is in<br>
&lt;fantasai> :is(), :where(), and :not() are the set in question<br>
&lt;dael> TabAtkins: You can use is in a compund context, but it has to be compound too. That way you can't smuggle in a more complicated selector<br>
&lt;dael> TabAtkins: Have spec text. Need approval<br>
&lt;TabAtkins> also :nth-child() i think<br>
&lt;dael> astearns: Text is in last comment. seems good to me<br>
&lt;dael> astearns: Other opinions?<br>
&lt;dael> astearns: Prop: Accept this restriction and the edit that defines it<br>
&lt;dael> fantasai: Kind of more of an expansion. Previously only allowed some things and adds :is and :where<br>
&lt;dael> TabAtkins: Lot of places where they were allowed but could contain whatever. But doesn't matter<br>
&lt;dael> astearns: Prop: Accept the edit<br>
&lt;dael> astearns: Obj?<br>
&lt;dael> RESOLVED: Accept the edit<br>
</details>


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


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

Received on Thursday, 5 January 2023 00:20:07 UTC