- From: Peter Linss via GitHub <sysbot+gh@w3.org>
- Date: Thu, 22 Dec 2022 00:29:00 +0000
- To: public-css-archive@w3.org
My point about idents isn't that it's hard, it's that it's _one more thing_. i.e. the syntax exceptions aren't 'just one simple rule'. (Also, you forgot that idents can start with escapes, underscores, and non-ascii...) The rules at this point are: 1) if your selector doesn't start with an ident, use as-is (and know what an ident is), or optionally prefix with `&` 2) if it starts with an ident, you must prefix with `&` 3) unless you need to use `&` somewhere else inside your selector, the wrap the first selector in `:is()` (And, really, is adding `:is()` all the time an improvement? I know you're not seriously expecting people to just always wrap the first selector in `:is()`, but I can see tools doing it.) Prepending every nested rule with `@` actually _is_ one simple rule and there's no special casing, ever. Every selector syntax available now or in the future 'just works' (we already excluded `@` from selectors) and there are no conflicts with future extensions to property syntax. -- GitHub Notification of comment by plinss Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8249#issuecomment-1362251766 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 22 December 2022 00:29:02 UTC