Re: [csswg-drafts] [selectors4] Name the “functional pseudo-class like :matches() with 0 specificity”

I have a strong feeling this repeats mistakes from CSS2, when pseudo-classes and pseudo-elements were the same thing syntactically (remember `:after` and `::after`?). Now with introduction of functional selectors they have exactly the same syntactic form for as pseudo-classes. But when we get one more functional selector (like a negative `:is`) and then another one and another one it becomes hard to distinguish ones that affect specificity and ones that do not.

GitHub Notification of comment by CyberAP
Please view or discuss this issue at using your GitHub account

Received on Thursday, 5 July 2018 14:51:05 UTC