- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Dec 2022 02:26:29 +0000
- To: public-css-archive@w3.org
> I strongly disagree that your Category 4 is just "lax syntax in preprocessors". The underlying reason for Nesting to exist is to reduce repetition. I added `5 reduce repetition` as a specific category. You are right that there is a need for this outside of the other categories. I had something very specific in mind with `4` but I clearly didn't express that well :) I have added more comparisons which might help? ----- > Losing those other categories would be a huge limitation and render the feature much less attractive. I think this needs to be considered for CSS as a whole. Which is why other features like `@scope` and `@custom-selector` could be taken into account. Does CSS as a whole meet the needs previously filled by nesting in preprocessors? This in contrast with : Does nesting in browsers meet the needs previously filled by nesting in preprocessors? -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8166#issuecomment-1334684279 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 December 2022 02:26:31 UTC