- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Dec 2020 16:26:06 +0000
- To: public-css-archive@w3.org
So the proposal is that a bare `@nest` with no selector creates a rule that cannot contain any declarations but only CSS rules, which are all assumed to be [nest-containing](https://drafts.csswg.org/css-nesting/#nest-containing)? I wouldn't be opposed to that. It would save quite a few characters in nested rules with high breadth and low depth, and would make them easier to read too without the repetitive `@nest`. Do note however that @tabatkins has objected to defaulting to descendant selectors when no `&` is present, and his [arguments](https://github.com/w3c/csswg-drafts/issues/5738#issuecomment-736750108) are quite sound. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4748#issuecomment-746579516 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 December 2020 16:26:08 UTC