Bug Tracker

#7566 closed bug (invalid)

Opened November 19, 2010 09:58AM UTC

Closed November 20, 2010 03:00AM UTC

nth-last-child does not return the same results as document.querySelectorAll

Reported by: anonymous Owned by: anonymous
Priority: undecided Milestone: 1.5
Component: unfiled Version: 1.4.4
Keywords: Cc:
Blocked by: Blocking:
Description

p:nth-last-child(2n) or p:nth-last-child(odd)

native chrome/firefox:173

jquery:162

p:nth-last-child(2n+1) or p:nth-last-child(even)

native chrome/firefox:151

jquery:162

Attachments (0)
Change History (5)

Changed November 19, 2010 10:01AM UTC by snover comment:1

owner: → anonymous
status: new → pending

This is not a useful bug report. Please follow the bug reporting guidelines and create a reduced test case. Thanks!

Changed November 19, 2010 11:26AM UTC by anonymous comment:2

status: pending → new

my bad, it was the other way around:

p:nth-last-child(2n) or p:nth-last-child(odd)

native chrome/firefox/safari:162

jquery:173

p:nth-last-child(2n+1) or p:nth-last-child(even)

native chrome/firefox/safari:162

jquery:151

so this is a bug in browsers right? not the other way round?

Replying to [ticket:7566 anonymous]:

p:nth-last-child(2n) or p:nth-last-child(odd) native chrome/firefox:173 jquery:162 p:nth-last-child(2n+1) or p:nth-last-child(even) native chrome/firefox:151 jquery:162

Changed November 19, 2010 12:06PM UTC by jitter comment:3

status: new → pending

Thanks for taking the time to contribute to the jQuery project! But still haven't submitted a test case to reproduce your bug, only something which I guess is your debug output.

Please submit a reduced test case which reproduces the issue you are experiencing (ideally on http://jsfiddle.net).

So that we can investigate this issue further.

----- -----

How to report bugs

Changed November 20, 2010 02:52AM UTC by anonymous comment:4

status: pending → new

i can not reproduce the problem. it must be in my tests where for some reasons in other 100s of selectors nth-last-child starts giving different result so i guess you can forget about it! sorry!

Changed November 20, 2010 03:00AM UTC by addyosmani comment:5

resolution: → invalid
status: new → closed

As the original ticket submitter has indicated this bug cannot be reproduced and we haven't been provided a complete test case that reproduces it, I am closing this ticket as invalid.