Skip to main content

Bug Tracker

Side navigation

#7452 closed bug (fixed)

Opened November 09, 2010 09:50PM UTC

Closed December 06, 2010 09:41PM UTC

Last modified March 13, 2012 04:18PM UTC

Next Adjacent/Sibling Selectors no longer work without "prev" element

Reported by: ambrauer Owned by: jitter
Priority: high Milestone: 1.5
Component: selector Version: 1.4.3
Keywords: sibling next previous Cc:
Blocked by: Blocking:

Using the next selectors (adjacent and siblings) with a context or find no longer seems to be working in version 1.4.3+.

See an example in jsFiddle here.

What's odd is that it still works for the child selector which has a similar syntax.

Attachments (0)
Change History (5)

Changed November 10, 2010 04:35PM UTC by SlexAxton comment:1

component: unfiledselector
keywords: → sibling next previous
priority: undecidedlow
status: newopen

This seems valid. Definitely a regression. (Though technically these are not valid qSA compatible selectors, which is why they've gotten a little wonky. If you just write out the full selector, like the 3rd example, it'll work just fine.)

Changed November 10, 2010 07:46PM UTC by SlexAxton comment:2

#7463 is a duplicate of this ticket.

Changed December 02, 2010 02:32PM UTC by jitter comment:3

#7682 is a duplicate of this ticket.

Changed December 02, 2010 04:00PM UTC by jitter comment:4

owner: → jitter
priority: lowhigh
status: openassigned

This bug (as stated above) only affects the hierarchy-selectors next adjacent/siblings selectors (+/~) when used with a context but with no left hand side.

This bug is caused by changes for 1.4.3 to allow qSA to be used for Element-rooted queries too.

test case\\\\

test case\\\\

Sizzle pull request

Changed December 06, 2010 09:41PM UTC by john comment:5

resolution: → fixed
status: assignedclosed