Modify ↓
Ticket #3924 (closed bug: fixed)
(nth/first/last)-child selector bug
| Reported by: | LosT | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 1.3.1 |
| Component: | selector | Version: | 1.3 |
| Keywords: | Cc: | ||
| Blocking: | Blocked by: |
Description
Manipulating the dom after *-child selector may break sequent *-child selectors if the number of childs remains the same.
---
I think this is caused by caching in filter.CHILD, here: var doneName = "child" + parent.childNodes.length;
Changing it to var doneName = match[0];
(which i saw is set in preFilter.CHILD) should fix the problem.
Also, parent.childNodes.length is painfully slow on explorer. This change should speed up IE (and slow down the other browsers).
Attachments
Change History
Changed 4 years ago by LosT
-
attachment
test2.html
added
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.
Note: See
TracTickets for help on using
tickets.

Test case