Side navigation
#11898 closed bug (fixed)
Opened June 12, 2012 01:19PM UTC
Closed July 25, 2012 01:47AM UTC
Last modified July 25, 2012 01:48AM UTC
prevAll() with a complicated :not() selector returns results in wrong order
Reported by: | joed@epurchasepower.com | 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:
I confirmed it in Chrome 19 and Firefox 10 on Windows 7.
Attachments (0)
Change History (3)
Changed June 12, 2012 03:30PM UTC by comment:1
component: | unfiled → manipulation |
---|---|
milestone: | None → 1.next |
priority: | undecided → low |
status: | new → open |
Changed July 25, 2012 01:47AM UTC by comment:2
resolution: | → fixed |
---|---|
status: | open → closed |
This appears to have been fixed with the Sizzle rewrite(s) in 1.8.
Changed July 25, 2012 01:48AM UTC by comment:3
milestone: | 1.next → 1.8 |
---|