- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Dec 2022 00:36:22 +0000
- To: public-css-archive@w3.org
> One other advantage to this proposal, `@nest` is something that authors can enter into a search engine when they encounter it in the wild for the first time. (It also provides context to figure it out on their own.) > > An author seeing: > [snip] > has no keywords any search engine is going to provide reasonable results for (and no obvious indication that nesting is happening, either could be interpreted as typos). CSS is full of symbols that have the same issue: `#id`, `.class`, `[foo]` etc Also, googling "ampersand css" would probably work fine (as evidenced by the [current results](https://www.google.com/search?q=ampersand+css) which are about nesting in preprocessors). -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7970#issuecomment-1332948607 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 00:36:24 UTC