W3C home > Mailing lists > Public > www-style@w3.org > April 2013

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

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 17 Apr 2013 15:07:52 -0700
Message-ID: <CAAWBYDAZM_=kDt0Ei9gn5q+94KmWx5+gWi5exmPOruedFt6z4A@mail.gmail.com>
To: Fran├žois REMY <francois.remy.dev@outlook.com>
Cc: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
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
Received on Wednesday, 17 April 2013 22:08:38 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 17 April 2013 22:08:39 UTC