Bug Tracker


Ticket #11898 (closed bug: fixed)

Opened 22 months ago

Last modified 21 months ago

prevAll() with a complicated :not() selector returns results in wrong order

Reported by: joed@… Owned by:
Priority: low Milestone: 1.8
Component: manipulation Version: 1.7.2
Keywords: Cc:
Blocking: Blocked by:


When I use a selector in prevAll that has a :not() with multiple classes, like :not(.unwanted,.skip), the results are returned in document order, rather than closest-first (i.e., reverse document order). It can be seen in this simple jsFiddle:


I confirmed it in Chrome 19 and Firefox 10 on Windows 7.

Change History

comment:1 Changed 22 months ago by dmethvin

  • Priority changed from undecided to low
  • Status changed from new to open
  • Component changed from unfiled to manipulation
  • Milestone changed from None to 1.next

comment:2 Changed 21 months ago by dmethvin

  • Status changed from open to closed
  • Resolution set to fixed

This appears to have been fixed with the Sizzle rewrite(s) in 1.8.

comment:3 Changed 21 months ago by dmethvin

  • Milestone changed from 1.next to 1.8

Please follow the  bug reporting guidlines and use  jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.


Add a comment

Modify Ticket

as closed

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.