- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Oct 2022 17:40:29 +0000
- To: public-css-archive@w3.org
> Using something like `&& { rules }` instead of `{ rules }` solves that problem (you can prepend a selector with no ambiguity) but then people don't like excessive ascii...
That would be *extremely* confusing for selector lists. E.g. here:
```css
a, b && {
.foo {
/* ... */
}
}
```
The "generated" selector is conceptually `a .foo, b .foo` (actually it is `:is(a, b) .foo`), but it *looks* like it would be `a, b .foo`.
--
GitHub Notification of comment by LeaVerou
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7834#issuecomment-1282773670 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 October 2022 17:40:31 UTC