- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Jan 2020 17:02:11 +0000
- To: public-css-archive@w3.org
> The selector-specificity `:where()` approach is both narrowly-applied and removes all specificity, which could still be a useful tool within origins Its goal is exactly the opposite: because it's a pseudo-class, it allows only removing *part* of the selector from the specificity calculation, enabling authors to distinguish importance-signifying criteria from merely filtering criteria. Of course it can be used for the whole selector, but it doesn't have to be, nor was that the primary use case I had in mind when I proposed it. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4470#issuecomment-577285060 using your GitHub account
Received on Wednesday, 22 January 2020 17:02:12 UTC