- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Oct 2022 17:13:40 +0000
- To: public-css-archive@w3.org
> Just because this will be burried in the call otherwise, I also came up with another variation of 1 that might solve its weirdest syntactic edge-case is: getting rid of @nest and allow & to appear in the selector twice (one at the start, and optionally one inside which is the actual place the replacement occurs in the rare cases where you need that). Every selector always start with & that way, this is consistent and easy to teach. I guess this would cont as 1b in the proposal nomenclature.
Using `&` multiple times is valid :
```css
.foo {
&:has(> &) {}
&:is(& .other) {}
& + & {}
}
```
--
GitHub Notification of comment by romainmenke
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7834#issuecomment-1284330208 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 October 2022 17:13:42 UTC