Hi Ricardo,
My guess is that he's using multiple class names and that's why it
wasn't working originally (false positives); see my post a couple
back.
--
T.J. Crowder
tj / crowder software / com
Independent Software Engineer, consulting services available
On Mar 19, 12:54 am, ricardobeat wrote:
Your example is working fine for me with 1.3.2 - $('a[class!
=whatever]'). $('a[className!=whatever]') should also work.
cheers,
- ricardo
On Mar 18, 9:26 am, will wrote:
> Hi,
> Using :not() worked great.
> Cheers
> Will
>
> On Mar 18, 11:09 am, "T.J. Crowder" wrote:
>
> > Hi again,
>
> > *bl
Hi,
Using :not() worked great.
Cheers
Will
On Mar 18, 11:09 am, "T.J. Crowder" wrote:
> Hi again,
>
> *blush* Those same docs tell us that != is also supported by Sizzle.
> Note, though, that:
>
> a[class!=whatever]
>
> ...is the same as
>
> a:not([class=whatever])
>
> ...which is *not*
Hi again,
*blush* Those same docs tell us that != is also supported by Sizzle.
Note, though, that:
a[class!=whatever]
...is the same as
a:not([class=whatever])
...which is *not* the same as
a:not(.whatever)
...because of multiple class names. Example: With these links:
one
tw
Hi,
Is there a != attribute operator? I don't see it in either the CSS2
or CSS3 specs.[1][2] So I'm thinking that since jQuery 1.3 completely
replaced the selector engine[3], there was a non-standard (but
useful!) extension to the syntax in v1.2 that didn't get carried
forward.
The good news i
5 matches
Mail list logo