- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Jan 2023 18:05:38 +0000
- To: public-css-archive@w3.org
Yeah, after discussing with @nex3 (the situation doesn't apply to Sass, since it doesn't have forgiving parsing anywhere), I do lean towards Option 2 as well. To handle the rare weird case where it will matter, I'll probably have to specify some sort of "guaranteed never-matching selector" that can be paired with &, and specify that an `:is()` has to insert that if it would drop an invalid selector that contains an `&` token and none of the remaining valid selectors have it, but that's a corner case we don't need to worry about imminently. (That is, `:is(:unknown(&), .bar)` would serialize to `:is(&:matches-nothing, .bar)` instead, but `:is(:unknown(&), & .bar)` would just serialize to `:is(& .bar)` as normal.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7972#issuecomment-1382205074 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 13 January 2023 18:05:40 UTC