On this point I disagree. The previous version was equal to: li:not([class=zoom])
The current version is equal to: li[class]:not([class=zoom]) This change came about after discussing it over with the MochiKit team (since they use the same selector engine as us) and I have to agree with their implementation: Every single attribute selector at least tests for the presence of the attribute - everything after that is just filtering. Considering how easy it is to get "every element that does not have an attribute equal to this value - and does not have the attribute itself": li:not([class=zoom]) it seems like an acceptable change. --John On Thu, Jan 15, 2009 at 8:50 AM, prefect <[email protected]> wrote: > > The documentation for the [attr!=value] filter reads: "Matches > elements that either don't have the specified attribute or do have the > specified attribute but not with a certain value." > > In 1.2.6 $("li[class!='zoom']") would give me both LI elements without > a class attribute and those with a class attribute not equal to > 'zoom'. In 1.3 I only get LI elements with a class attribute defined > (and not equal to 'zoom'). To me this seems like a bug, and not the > best behaviour. It's also in conflict with the expected behaviour > described in the documentation. > > I'm a bit new to jQuery development, so if I have wrong expectations > or there's a better way for this, please enlighten me. But I thought > I'd report this in case it really is a bug in Sizzle or jQuery 1.3. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
