The CSS2 and CSS3 specs disagree on this, annoyingly enough.  I'd
originally written ":not" to throw an exception on selectors with more
than one token, but then I saw the conflicting definitions and
relented. All the other major libraries seem to allow this confusing
Not being able to use the descendant combinator after a :not clause,
however, is a bug. Wiktor, feel free to report it; I'll try to fix it
before 1.6 final.
On Sep 26, 10:51 am, kangax <[EMAIL PROTECTED]> wrote:
> >From w3c specs (http://www.w3.org/TR/2001/CR-css3-selectors-20011113/
> "The negation pseudo-class is a functional notation taking a simple
> selector (excluding the negation pseudo-class itself and pseudo-
> elements) as an argument."
> Now what is simple selector (http://www.w3.org/TR/2001/CR-css3-
> selectors-20011113/#simple-selectors-dfn) ?
> "A simple selector is either a type selector, universal selector,
> attribute selector, ID selector, content selector, or pseudo-class.
> One pseudo-element may be appended to the last sequence of simple
> Looks like your 'a:not(a[rel$="nofollow"]' is not quite a simple
> selector (but rather a combination of type and attribute ones)
> Besides, a:not(a[rel^=external]) doesn't make sense in the first place
> (just like div:not(div) which will never match) : )
> Why select <a> that are not <a> with some condition when you could
> just specify condition on its own. It will be tested against all <a>
> anyway: a:not([rel^=external])
> Hope this helps,
You received this message because you are subscribed to the Google Groups
"Prototype: Core" group.
To post to this group, send email to firstname.lastname@example.org
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at