- From: Devon Govett via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Oct 2022 07:02:33 +0000
- To: public-css-archive@w3.org
Is it out of the question to simply only allow (and require) `&` at the start of a nested selector? I feel the utility and readability of `&` in other positions isn't that great anyway. Maybe it's better not to nest these selectors but to write them out fully as separate non-nested rules. That would eliminate the need for `@nest` and simplify the syntax, while improving readability IMO. -- GitHub Notification of comment by devongovett Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7834#issuecomment-1283528268 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 07:02:35 UTC