- From: Ilya Streltsyn via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Jul 2018 13:34:15 +0000
- To: public-css-archive@w3.org
> one option was to have a specificity parameter in :matches Was the option of having one pseudo-class with optional specificity parameter (regardless its exact name), instead of two almost identical in anything except specificity pseudo-classes, rejected completely? Since the specificity rules of `:matches()` [have already been redefined](https://github.com/w3c/csswg-drafts/issues/1027#issuecomment-393236516), so compatibility with existing implementations is not required anymore, maybe this option could have a second chance? -- GitHub Notification of comment by SelenIT Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2143#issuecomment-402480888 using your GitHub account
Received on Wednesday, 4 July 2018 13:34:18 UTC