- From: Peter Linss via GitHub <sysbot+gh@w3.org>
- Date: Sat, 26 Nov 2022 20:31:52 +0000
- To: public-css-archive@w3.org
Ok, in my original thinking `&` in this proposal would only be used to denote a rule matching the selector in the `@nest` rule, but I can see the use cases for allowing it in other nested rules, especially for the pseudo-element usage. So we can allow the `&` to appear (zero or one times) in any nested rule. If not present, it defaults to being at the front with a space combinator. I disagree with the added indenting being a problem however, all modern code editors can indent and un-indent blocks with a single keystroke, and any decent diff tool will also clearly show changes as being whitespace-only. I don't see this a burden on developers (in fact, showing that something is now the root of a nesting context in a diff may actually be useful). I still think this proposal deserves consideration as it neatly side-steps all the other issues with the other nesting proposals. -- GitHub Notification of comment by plinss Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7970#issuecomment-1328109428 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 26 November 2022 20:31:54 UTC