12339 2007-01-19 22:24:22 -0800 XML DOM operations involving two documents don't match IE/Firefox behavior 2022-08-05 15:16:48 -0700 1 1 1 Unclassified WebKit DOM 420+ Mac OS X 10.4 RESOLVED CONFIGURATION CHANGED P2 Normal --- 10489 1 jesse webkit-unassigned ahmad.saleem792 ap bfulgham cdumez rniwa spocke oldest_to_newest 34163 0 jesse 2007-01-19 22:24:22 -0800 I think that Safari probably has the more spec-compliant implementation but I report this for the sake of cross-browser AJAX compatibility. appendChild, insertBefore, replaceChild, and setAttributeNode (could there be more?) fail when the argument is a node from a different XML document. In IE and Fx these methods behave as though the nodes are in the same document. No special logic is necessary to test whether the ownerDocument property of the two nodes is the same. The work around is to use importNode(), call one of the above methods passing in the imported node, and remove the argument node from its parent node in the other document. 22956 1 mjs 2007-02-16 20:48:24 -0800 Our behavior is more spec-compliant. We would consider changing it, but I think Firefox at least is considering changing to match the spec more closely instead 109833 2 27689 ap 2009-02-16 02:47:02 -0800 Created attachment 27689 test case On this test case, WebKit and IE7 raise an exception, while Firefox 3.1b2 and Opera 9.63 do not. I'm not sure if that's the case reported here. 109834 3 ap 2009-02-16 02:47:51 -0800 See also: bug 4569. 142859 4 spocke 2009-08-26 08:33:37 -0700 I don't think this is a bug. You should use importNode if you want to add a node from one document to another according to W3C specs. 1502951 5 lforschler 2019-02-06 09:03:21 -0800 Mass moving XML DOM bugs to the "DOM" Component. 1889243 6 ahmad.saleem792 2022-08-05 15:16:37 -0700 I am unable to reproduce this bug based on expected results since the behavior of Safari 15.6 on macOS 12.5 matches with other browsers (Chrome Canary 106 and Firefox Nightly 105) on attached test cases. It shows a dialog box with "P" in it and then show two empty iframe and it is same across all browsers. Since all browsers are working same, I am going to mark this as "RESOLVED CONFIGURATION CHANGED" expecting that something along the lien fixed it. In case if I am testing incorrectly, please reopen this bug. Thanks! 27689 2009-02-16 02:47:02 -0800 2009-02-16 02:47:02 -0800 test case move-node.html text/html 449 ap PGJvZHkgb25sb2FkPSJ0ZXN0KCkiPgo8c2NyaXB0PgpmdW5jdGlvbiB0ZXN0KCkgewogICAgdmFy IGRvYzEgPSBmcmFtZXNbMF0uZG9jdW1lbnQ7CiAgICB2YXIgZG9jMiA9IGZyYW1lc1sxXS5kb2N1 bWVudDsKICAgIGRvYzIuYm9keS5hcHBlbmRDaGlsZChkb2MyLmNyZWF0ZUVsZW1lbnQoInAiKSk7 CgogICAgdHJ5IHsKICAgICAgICBkb2MxLmJvZHkuYXBwZW5kQ2hpbGQoZG9jMi5ib2R5Lmxhc3RD aGlsZCk7CiAgICAgICAgYWxlcnQoZG9jMS5ib2R5Lmxhc3RDaGlsZC50YWdOYW1lKTsKICAgIH0g Y2F0Y2ggKGV4KSB7CiAgICAgICAgYWxlcnQoZXguZGVzY3JpcHRpb24gPyBleC5kZXNjcmlwdGlv biA6IGV4KTsKICAgIH0KfQo8L3NjcmlwdD4KPGlmcmFtZSBzcmM9ImFib3V0OmJsYW5rIj48L2lm cmFtZT4KPGlmcmFtZSBzcmM9ImFib3V0OmJsYW5rIj48L2lmcmFtZT4KPC9ib2R5Pgo=