Bug Tracker

Opened 5 years ago

Closed 5 years ago

#12337 closed bug (fixed)

:nth-child selector not accurate after new child element added

Reported by: bobbymwalters@… Owned by: gibson042
Priority: high Milestone: 1.8.2
Component: selector Version: 1.8.0
Keywords: Cc:
Blocked by: Blocking:

Description

Using the :nth-child selector after a new child element has been added to a parent isn't working correctly in 1.8.0. However, with 1.7.2 the same scenario works as expected.

A test for using .find vs .children was added as well because in 1.7.2 using .children('.class:nth-child(NUMBER)') was significantly faster in Internet Explorer.

It seems the .find vs .children is also being handled differently. Using 1.8.0 the .find variant works in Chrome 21.0.1180.79 but .children remains incorrect.

I've only ran this against Internet Explorer 8 and Chrome 21.0.1180.79. Thanks for your time!

jsFiddle: http://jsfiddle.net/yVe4H/1/

Change History (6)

comment:1 Changed 5 years ago by dmethvin

Component: unfiledtraversing
Milestone: None1.8.1
Priority: undecidedblocker
Status: newopen

Confirmed. Here's an updated fiddle: http://jsfiddle.net/dmethvin/yVe4H/2/

comment:2 Changed 5 years ago by timmywil

Component: traversingselector
Resolution: duplicate
Status: openclosed

Duplicate of #12205.

comment:3 Changed 5 years ago by gibson042

Milestone: 1.8.11.8.2
Priority: blockerhigh
Resolution: duplicate
Status: closedreopened

comment:4 Changed 5 years ago by gibson042

Owner: set to gibson042
Status: reopenedassigned

comment:5 Changed 5 years ago by dmethvin

#12474 is a duplicate of this ticket.

comment:6 Changed 5 years ago by Timmy Willison

Resolution: fixed
Status: assignedclosed

Update Sizzle: fix position caching with child selectors. Fixes #12337.

Changeset: 99f4825707e2bf6f19598a00f53d58ef3878190c

Note: See TracTickets for help on using tickets.