Nope, we're staying with the current functionality. We made the change to make [name!=value] equivalent to [name]:not([name=value]) after some discussion with other frameworks but reverted it when it became apparent that the result was very non-obvious and broke a lot of jQuery code. We're keeping [name!=value] equal to :not([name=value]).
--John On Fri, Jan 23, 2009 at 6:36 AM, shaw...@gmail.com <shaw...@gmail.com> wrote: > > In the docs it shows that [attr!=value] Matches elements that have the > specified attribute but not with a certain value. > (http://docs.jquery.com/Selectors/attributeNotEqual#attributevalue) > But in the recent changes in jQuery 1.3.1,it seems to revert. > (http://dev.jquery.com/changeset/6149) > > So I just wonder whether it will change again? > thx~ > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
