- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Fri, 29 Dec 2017 12:19:51 +0000
- To: public-css-archive@w3.org
> `:nospecificity` is ridiculously long and prevents any possibility of expansion in the future to allow setting specificity, as @tabatkins suggested. At least the latter point could be avoided, of course, by using `:specificity()` instead. Nonetheless it's still very long and hard to write. So, I also vote for `:is()`, even when it rather indicates a check and not something to _set_ the specificity. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2143#issuecomment-354439317 using your GitHub account
Received on Friday, 29 December 2017 12:19:53 UTC