Skip to main content

Bug Tracker

Side navigation

#9611 closed bug (cantfix)

Opened June 17, 2011 06:21PM UTC

Closed July 12, 2011 06:09PM UTC

Selectors don't work properly on Chrome

Reported by: David Owned by: David
Priority: low Milestone:
Component: selector Version: 1.6.1
Keywords: Cc:
Blocked by: Blocking:


We're having major issues with selectors and how they work in Chrome.

:nth-child(x) does not seem to be working properly always.

Please have a look at forum topic which also provides links to jsFiddle demos...

Attachments (0)
Change History (6)

Changed June 17, 2011 08:03PM UTC by timmywil comment:1

component: unfiledselector
owner: → David
priority: undecidedlow
status: newpending

Thanks for taking the time to contribute to the jQuery project! Please be more specific and provide a reduced failing test case without the unnecessary ajax code so that we can see the issue intended for review.

Here is a test case to get started, but the selectors I tried work fine:

Changed June 17, 2011 08:42PM UTC by comment:2

Hi Timmy,

This will probably illustrate more what my issue is:

Please let me know if this is unclear still...

Changed June 17, 2011 09:52PM UTC by timmywil comment:3

status: pendingopen

Changed June 20, 2011 10:36AM UTC by flexin comment:4

Hi Timmy,

Just so I know - I noticed this was tagged as low priority (I don't want to interfere with those evaluations, as you probably do have more important bugs to attend to...)

However - what timeframe should I be looking at for a fix for this issue?

Changed June 20, 2011 02:13PM UTC by timmywil comment:5

It might get tackled in 1.7, but probably not until then.

Changed July 12, 2011 06:09PM UTC by john comment:6

resolution: → cantfix
status: openclosed

There have been a number of issues regarding :nth-child() usage in WebKit - it sounds like they're working to fix them and should be coming soon.