- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Oct 2022 22:19:23 +0000
- To: public-css-archive@w3.org
> I don't understand what you mean by this. .foo { .bar & {...} } will match the same elements in both contexts (equivalent to .bar .foo).
```css
.bar .foo {
@nest .other & {
color:green;
}
}
```
css: `.other :is(.foo .bar)`
sass: `.other .foo .bar`
> But these are probably already ruled out anyway, due to people using garbage to "comment out" their properties, like `//color: red;`, or `*color:red;` for an old IE hack
> I'm not sure I understand what you mean. We can continue to innovate in any way that doesn't make properties start with a non-ident (already probably necessary) or rules start with idents. All your examples, and all similar ones with new selectors or combinators, will be fine in the future.
I am maybe misunderstanding the first quoted statement. So maybe it is fine if `*` was used for some IE hack.
--
GitHub Notification of comment by romainmenke
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7834#issuecomment-1275341169 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 October 2022 22:19:24 UTC