- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Dec 2022 01:49:28 +0000
- To: public-css-archive@w3.org
> > CSS is full of symbols that have the same issue: #id, .class, [foo] etc > > Doesn't mean we're doing people any favors by adding more... (in fact, there's even a TAG [design principle](https://w3ctag.github.io/design-principles/#leave-the-web-better) about this :-) My point wasn't "there is precedent for this bad thing and thus it's fine", it was "CSS already does this and authors don't seem to have any trouble googling things". So I don't think the TAG principle you linked applies here. Learnability is one component of usability, efficiency is another, equally important one. For commonly typed things, brevity becomes more important than learnability. > Another point, how would proposals 3 & 4 be [feature detectable](https://w3ctag.github.io/design-principles/#feature-detect)? (I accept it can likely be done, but in an obvious way?) `@supports selector(&)`? -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7970#issuecomment-1333035321 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 01:49:31 UTC