W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2018

[csswg-drafts] [css-selectors] Why does `:is()` have the specificity of the most specific selector in its arguments?

From: ExE Boss via GitHub <sysbot+gh@w3.org>
Date: Thu, 15 Nov 2018 11:05:14 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-381110197-1542279913-sysbot+gh@w3.org>
ExE-Boss has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-selectors] Why does `:is()` have the specificity of the most specific selector in its arguments? ==
https://drafts.csswg.org/selectors-4/#matches

I believe it would make more sense if the specificity would be identical to that when the selector would be expanded into all possible combinations, which also makes [polyfilling using PostCSS](https://github.com/postcss/postcss-selector-matches) easier.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3325 using your GitHub account
Received on Thursday, 15 November 2018 11:05:16 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:26:54 UTC