Skip to main content

Bug Tracker

Side navigation

#14043 closed bug (notabug)

Opened June 19, 2013 11:12PM UTC

Closed July 04, 2013 05:24PM UTC

$('#root').find(':not(#nested) > li') fails

Reported by: ngryman Owned by: timmywil
Priority: high Milestone: None
Component: selector Version: 2.0.2
Keywords: Cc:
Blocked by: Blocking:

This selector fails with the following html structure:

<ul id="root">
    <ul id="nested">

The QSA version works fine.

But if I change the container to a superior level (i.e. body) this works fine:

$('body').find(':not(#nested) > li')

It seems this selector does not work with direct children.

Here is a jsfiddle that illustrates the bug :

It fails for any version of jQuery.


Attachments (0)
Change History (5)

Changed June 19, 2013 11:41PM UTC by gibson042 comment:1

#14044 is a duplicate of this ticket.

Changed June 20, 2013 12:16AM UTC by gibson042 comment:2

cc: → timmywil
status: newopen

Confirmed. Sizzle's qSA path returns empty when it seems like it shouldn't be. The cause might be really obvious, but I'm just not seeing it—nor am I seeing a good way to catch it. Can someone else weigh in?

Changed June 20, 2013 05:34PM UTC by ngryman comment:3

Oups sorry, I've posted it twice...

Changed July 04, 2013 05:13PM UTC by timmywil comment:4

cc: timmywil
component: unfiledselector
owner: → timmywil
priority: undecidedhigh
status: openassigned

Changed July 04, 2013 05:24PM UTC by timmywil comment:5

resolution: → notabug
status: assignedclosed

This is not a bug. This is the scope issue with QSA being demonstrated. Sizzle's result is the correct one since #root should be the context.

Read the selector like this:

find children that are not #nested that contain any li's as direct descendants. #root does not have any children that are not #nested that contain lis. It only contains #nested and lis.