Side navigation
#12337 closed bug (fixed)
Opened August 17, 2012 09:20PM UTC
Closed September 19, 2012 04:04PM UTC
:nth-child selector not accurate after new child element added
| Reported by: | bobbymwalters@gmail.com | 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:
Attachments (0)
Change History (6)
Changed August 21, 2012 12:24AM UTC by comment:1
| component: | unfiled → traversing |
|---|---|
| milestone: | None → 1.8.1 |
| priority: | undecided → blocker |
| status: | new → open |
Changed August 27, 2012 04:07PM UTC by comment:2
| component: | traversing → selector |
|---|---|
| resolution: | → duplicate |
| status: | open → closed |
Duplicate of #12205.
Changed September 14, 2012 04:41AM UTC by comment:3
| milestone: | 1.8.1 → 1.8.2 |
|---|---|
| priority: | blocker → high |
| resolution: | duplicate |
| status: | closed → reopened |
Changed September 14, 2012 04:42AM UTC by comment:4
| owner: | → gibson042 |
|---|---|
| status: | reopened → assigned |
Confirmed. Here's an updated fiddle: http://jsfiddle.net/dmethvin/yVe4H/2/