Skip to main content

Bug Tracker

Side navigation

#3924 closed bug (fixed)

Opened January 20, 2009 01:55PM UTC

Closed January 21, 2009 10:02PM UTC

Last modified March 15, 2012 02:41PM UTC

(nth/first/last)-child selector bug

Reported by: LosT Owned by:
Priority: major Milestone: 1.3.1
Component: selector Version: 1.3
Keywords: Cc:
Blocked by: Blocking:

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 (1)
  • test2.html (0.5 KB) - added by LosT January 20, 2009 01:56PM UTC.

    Test case

Change History (1)

Changed January 21, 2009 10:02PM UTC by john comment:1

component: unfilledselector
resolution: → fixed
status: newclosed

Thanks for the test case, I just fixed this in SVN rev [6147].