Bug Tracker

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#11898 closed bug (fixed)

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:
Blocked by: Blocking:

Description

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:

http://jsfiddle.net/aMXJ6/

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

Change History (3)

comment:1 Changed 4 years ago by dmethvin

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

comment:2 Changed 4 years ago by dmethvin

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

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

comment:3 Changed 4 years ago by dmethvin

  • Milestone changed from 1.next to 1.8
Note: See TracTickets for help on using tickets.