#4158 closed bug (fixed)
multiple pseudo selector issues
| Reported by: | initjh | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 1.3.2 |
| Component: | selector | Version: | 1.3.1 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description (last modified by john)
:not(:nth-child(1))
See http://dev.jquery.com/ticket/4169 for: :has(:nth-child(1))
Change History (9)
comment:1 follow-up: ↓ 2 Changed 8 years ago by initjh
comment:2 in reply to: ↑ 1 Changed 8 years ago by initjh
Replying to initjh:
Seems I made a slight mistake, it only fails on :not(:nth-child(1)). Sorry.
Sorry, misread debugger. It does fail on :has(:nth-child(1)).
comment:3 Changed 8 years ago by dz
Simplified test case:
comment:4 Changed 8 years ago by initjh
Actually, that's a different problem. You should make a new ticket for that. I noticed that while testing on Chrome. The selector is processed in Chrome, but it selects the parent like you have shown.
This one is (I think) related to some RegEx problems in Sizzle, when you put :nth-child in :not or :has. Another example, :not(:not(:not(div))).
comment:5 Changed 8 years ago by initjh
Simplified test case, thanks for the test case site dz. http://jquery.nodnod.net/cases/124
comment:6 Changed 8 years ago by initjh
I found a way to make it behave properly: On the first iteration in Sizzle.filter, have it process PSEUDO type first instead of CHILD. It will then properly parse the :nth-child selector, and apply :not to it as expected.
comment:7 Changed 8 years ago by dz
comment:8 Changed 8 years ago by john
- Component changed from core to selector
- Resolution set to fixed
- Status changed from new to closed
Fixed in SVN rev [6212].
comment:9 Changed 8 years ago by john
- Description modified (diff)
Seems I made a slight mistake, it only fails on :not(nth-child(1)). Sorry.