- From: Peter Linss via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Dec 2022 05:04:12 +0000
- To: public-css-archive@w3.org
> 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. And in this proposal, even the `&` is not going to be needed that often (zero characters wins for brevity every time). The enclosing `@nest` will likely not get repeated enough to justify its removal/replacement. > Other places …in a selector? Yes, in principle it could be used in a selector in some context that isn't nesting. We have a limited number of ascii-friendly sigils to use and may need to repurpose it at some point. If the need is to detect the feature of nesting (or the other theoretical usage), it may not be enough to disambiguate. Being able to detect an actual at-rule is more specific, and more obvious. You also still never explained your initial objection about having to create a "whole separate rule" and the perceived componentization issue. -- GitHub Notification of comment by plinss Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7970#issuecomment-1333176875 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 05:04:14 UTC