Side navigation
#9293 closed bug (invalid)
Opened May 16, 2011 10:07AM UTC
Closed May 31, 2011 07:55AM UTC
Last modified December 12, 2013 08:50AM UTC
nth-child error on google chrome
Reported by: | nicola.gnecchi@hotmail.it | Owned by: | nicola.gnecchi@hotmail.it |
---|---|---|---|
Priority: | low | Milestone: | 1.next |
Component: | selector | Version: | 1.5.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
nth-child nested selector doesn't seem to work on chrome. Instead of opening "openLi"(openLi is an integer) element of the DOM, it opens the "opelLi+2" element, even if the alert of ".vertical-menu > li:nth-child("+openLi+") > ul").show()" shows its correctness. This script works perfectly on IE7,IE8,FIREFOX..
This is the script code:
$(function() { var openLi = $.cookie("open-menu-item"); if(openLi != null) { $(".vertical-menu > li:nth-child("+openLi+") > ul").show(); } });
Html code passed w3 validation..
Using "eq" instead of "nth-child" with "openLi - 1" will work.
Attachments (0)
Change History (3)
Changed May 16, 2011 02:50PM UTC by comment:1
component: | unfiled → selector |
---|---|
owner: | → nicola.gnecchi@hotmail.it |
priority: | undecided → low |
status: | new → pending |
Changed May 31, 2011 07:55AM UTC by comment:2
resolution: | → invalid |
---|---|
status: | pending → closed |
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!
Changed December 12, 2013 08:50AM UTC by comment:3
find that this is working in chrome, however the nth-last-child still gives me issues.
Thanks for taking the time to contribute to the jQuery project! Please provide a reduced test case on http://jsfiddle.net that reproduces the issue experienced to help us assess your ticket.
Additionally, test against the jQuery (edge) version to ensure the issue still exists.