Bug Tracker

Opened 12 years ago

Closed 11 years ago

Last modified 11 years ago

#11109 closed bug (fixed)

Sizzle: Expr.relative truncates prematurely

Reported by: gibson042 Owned by: Timmy Willison
Priority: high Milestone: 1.8
Component: selector Version: 1.7.1
Keywords: Cc:
Blocked by: Blocking:


Work on #10868 revealed this error in oldSizzle: http://jsfiddle.net/JBBM8/

Because Sizzle.selectors.relative functions "return" only a single match, Sizzle can be trapped into a false negative with respect to preceding parts of the full selector when the relative selector tests against multiple elements (e.g., "~" and "").

I'm pretty sure that fixing this will require changing the Sizzle.selectors.relative Extension API to allow "returning" arrays, so I will hold off working on this until the core team weighs in with their comments/approval.

Change History (10)

comment:1 Changed 12 years ago by gibson042

Technical explanation: Given a query like "A + B ~ C", Sizzle:

  1. Gets a set of all C, then
  2. Uses Sizzle.selectors.relative["~"] to replace each element with the first preceding sibling element matching B (or false if nonexistent), then
  3. Uses Sizzle.selectors.relative["+"] to replace each element with the preceding sibling element if it matches A (or false if it doesn't), then
  4. Returns all elements from the set at step 1 that stayed non-false through all subsequent steps

The problem here is that step 2 fails to report back all preceding siblings matching B, erroneously restricting the input set for subsequent step 3.

comment:2 Changed 12 years ago by dmethvin

Resolution: duplicate
Status: newclosed

Can you coordinate with timmywil on this? He's got #10697. I'll mark this one as a dup but really it seems like this should be filed as a Sizzle bug.

comment:3 Changed 12 years ago by dmethvin

Duplicate of #10697.

comment:4 Changed 11 years ago by Timmy Willison

Component: unfiledselector
Milestone: None1.next
Priority: undecidedhigh
Resolution: duplicate
Status: closedreopened

Reopening as this was not addressed in the rewrite. Here is another test case that i think is related:


Also see:


comment:5 Changed 11 years ago by Timmy Willison

Owner: set to Timmy Willison
Status: reopenedassigned

comment:6 Changed 11 years ago by Timmy Willison

OK, it seems the sibling issues from nwbox are already fixed, so those aren't related. However, there is still an issue with deeper levels. The fiddles are still valid.

comment:7 Changed 11 years ago by Timmy Willison

Milestone: 1.next1.8

A combination combinator fiddle for the masses: http://jsfiddle.net/timmywil/WSrGh/. Working on it.

comment:8 Changed 11 years ago by Timmy Willison

Resolution: fixed
Status: assignedclosed

comment:9 Changed 11 years ago by Timmy Willison

Update Sizzle. Fixes #11109.

Changeset: 8763bec032bc2dc10bf0d6686b820b731b525091

comment:10 Changed 11 years ago by Timmy Willison

#11079 is a duplicate of this ticket.

Note: See TracTickets for help on using tickets.