W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2020

Re: [csswg-drafts] [css-nesting] Conflicts in proposal with Sass/Less (#2937)

From: Evgeny Vrublevsky via GitHub <sysbot+gh@w3.org>
Date: Tue, 22 Dec 2020 14:56:04 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-749580547-1608648963-sysbot+gh@w3.org>
Current spec is close to perfect. I would probably make `@nest` mandatory to make it explicit, but the current spec allows to use `@nest` for every nested rule anyway.

If authors of CSS preprocessors want to allow mixing of the native CSS nesting and SCSS-like nesting in one file, they could rely on `@nest`. If there is `@nest` before nested selector, it means that a user wanted to use native CSS nesting. Nobody prohibits to use Sass / Less when the native CSS nesting is supported by browsers.

GitHub Notification of comment by vrubleg
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2937#issuecomment-749580547 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 22 December 2020 14:56:06 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:24 UTC