| Summary: | should be able to move a node from one document to another without calling adoptNode | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Ojan Vafai <ojan> | ||||
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | RESOLVED DUPLICATE | ||||||
| Severity: | Normal | CC: | abarth, ap, arv, darin, eric, hyatt, mitz, mjs | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | PC | ||||||
| OS: | OS X 10.5 | ||||||
| Attachments: |
|
||||||
Created attachment 65480 [details] test case You can do it now using adoptNode, but there's not reason we shouldn't allow a node to move from one document to another via appendChild. Firefox already allows this and it seems unlikely to me that there is code that depends on throwing an error here. Needing to worry about what document a node is coming from makes multi-document code considerably more complicated (e.g. needs to pass document objects around).