#6963 closed bug (fixed)
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 (last modified by )
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.
Change History (4)
comment:1 Changed 8 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 Changed 8 years ago by
| Description: | modified (diff) |
|---|
comment:3 Changed 8 years ago by
Can u test if it also finds children of detached elements as well. http://dl.dropbox.com/u/513327/bb-id.html
comment:4 Changed 7 years ago by
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:
Note: See
TracTickets for help on using
tickets.
Fixed http://github.com/jquery/jquery/commit/1ead20c2ed7cb4fd647d632ff9de8104669482de http://github.com/jeresig/sizzle/commit/6fd052b8010022761fdef312a068ddede96ce9bf