Bug 44639 - should be able to move a node from one document to another without calling adoptNode
Summary: should be able to move a node from one document to another without calling ad...
Status: RESOLVED DUPLICATE of bug 19524
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-25 15:14 PDT by Ojan Vafai
Modified: 2010-08-27 18:34 PDT (History)
8 users (show)

See Also:


Attachments
test case (308 bytes, text/html)
2010-08-25 15:14 PDT, Ojan Vafai
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ojan Vafai 2010-08-25 15:14:07 PDT
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).
Comment 1 Ojan Vafai 2010-08-27 18:34:37 PDT

*** This bug has been marked as a duplicate of bug 19524 ***