Re: [selectors4] :not and :matches specificity (was :not(a, b) vs. :not(a):not(b)

On Wed, Apr 17, 2013 at 1:28 PM, François REMY
<francois.remy.dev@outlook.com> wrote:
> The issue I see with max-of-selector instead of class-like priority is that I can increase the priority of a selector by any amount just by adding an always-true :not statement
>
>     a[href]:not(#undefined) {
>
>       // do I beat the "a#TheLink" selector?
>
>     }
>
> Or did I understand your proposal the wrong way?

Yes, that's the *current* behavior.  You have always been able to do
that, ever since :not() was first introduced.

~TJ