Side navigation
#6963 closed bug (fixed)
Opened August 27, 2010 07:10PM UTC
Closed August 27, 2010 07:16PM UTC
Last modified August 02, 2011 08:46PM UTC
Blackberry 4.6 Finds Nodes That No Longer Exist
Reported by: | john | Owned by: | |
---|---|---|---|
Priority: | Milestone: | 1.4.3 | |
Component: | selector | Version: | 1.4.2 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
See the test case here: http://ejohn.org/files/bugs/bb-id.html
Only seems to happen when the node has been in a cloned fragment.
Attachments (0)
Change History (4)
Changed August 27, 2010 07:16PM UTC by comment:1
resolution: | → fixed |
---|---|
status: | new → closed |
Changed August 27, 2010 07:22PM UTC by comment:2
description: | See the test case here: http://localhost:8888/jquery/id.html \ \ Only seems to happen when the node has been in a cloned fragment. → See the test case here: http://ejohn.org/files/bugs/bb-id.html \ \ Only seems to happen when the node has been in a cloned fragment. |
---|
Changed August 27, 2010 08:10PM UTC by comment:3
Can u test if it also finds children of detached elements as well.
Changed August 02, 2011 08:46PM UTC by comment:4
There is a bit of a possible BC break here, but I believe it only affects IE. Prior to this change, jQuery could find XML elements within the document; after this change, it cannot. Evidently, XML nodes in IE do not have a parentNode.
Please see the following fiddle:
Fixed http://github.com/jquery/jquery/commit/1ead20c2ed7cb4fd647d632ff9de8104669482de
http://github.com/jeresig/sizzle/commit/6fd052b8010022761fdef312a068ddede96ce9bf