#2847 closed bug (fixed)
jQuery :first-child selector does not work in IE if comment precedes element
Reported by: | westonruter | Owned by: | john |
---|---|---|---|
Priority: | major | Milestone: | 1.4 |
Component: | selector | Version: | 1.3.2 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
In MEIE 6/7/8b1, the :first-child selector does not work if a comment is the first child; it does not work using either pure CSS nor using the jQuery selector engine. Both, however, work in Firefox and Safari.
Test case: http://weston.ruter.net/projects/test-cases/jquery-first-child-bug/
Attachments (2)
Change History (8)
comment:1 Changed 15 years ago by
comment:2 Changed 15 years ago by
I've done a much more in-depth test case and determined that this is the only one of the similar selectors that exhibits this bug. It appears that .getElementsByTagName("*") returns comment nodes in IE. I'm working on a patch.
comment:3 Changed 15 years ago by
To fix this we're going to have to go slower and longer. A more clever patch might be better than the one I've just posted for review.
comment:4 Changed 13 years ago by
Component: | core → selector |
---|---|
Owner: | set to john |
comment:5 Changed 13 years ago by
Milestone: | 1.2.4 → 1.4 |
---|---|
Version: | 1.2.3 → 1.3.2 |
comment:6 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
This appears to have been fixed in 1.3.
The problem occurs because the first node returned for IE is the comment node. Here is my attempt at fixing it. (checked in IE6/7 and FF2/3).