- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Mon, 31 Oct 2022 04:27:13 +0000
- To: public-css-archive@w3.org
Aside (sorry) > If authors want to enforce that each selector in the list is unambiguous in case of edits they can use a linter to enforce this As a CSS author, I would prefer that a solution be found to remove the restriction on `<identifier>`, rather than having to remember it or to use a linter. Remember to start with `&` or `@nest` (option 1) seems less constraining. As a non-SASS/SCSS author, I also consider option 1 better because nested compound/descendant selectors are explicit. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7980#issuecomment-1296525054 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 31 October 2022 04:27:15 UTC