- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Dec 2022 04:02:57 +0000
- To: public-css-archive@w3.org
> CSS has rejected other uses of sigils in the past for precisely the searchability issue, and it's not necessarily obvious to an author to search for 'ampersand' instead of `&`. Brevity can be taken too far (see YAML), it is a tradeoff, but not an obvious one. And given that `@nest` mostly doesn't require the `&` it can easily result in less typing if there are enough nested rules, so proposal 3 doesn't necessarily win on brevity. Yes, because to use a symbol, the feature needs to be needed frequently enough that brevity is important. This is not true for every feature, but it certainly is for nesting. > > @supports selector(&)? > > Maybe, but seems fragile, what if there are other places `&` can be used? Other places …in a selector? > (and is it _really_ a selector?) Yes, it is. Really. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7970#issuecomment-1333132954 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 1 December 2022 04:02:59 UTC