RESOLVED CONFIGURATION CHANGED63538
Range.insertNode doesn't work per DOM 2 Range 
https://bugs.webkit.org/show_bug.cgi?id=63538
Summary Range.insertNode doesn't work per DOM 2 Range
Olli Pettay (:smaug)
Reported 2011-06-28 08:10:18 PDT
Per DOM 2 Range, and still per the new draft version of Range spec insertNode should not have special handling when comparing to normal DOM mutations. If range is collapsed and insertNode is called, the range object should not be modified. ACID3 accepts both this invalid behavior and the behavior defined in DOM 2 Range.
Attachments
testcase (732 bytes, text/html)
2011-06-28 08:10 PDT, Olli Pettay (:smaug) 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Olli Pettay (:smaug)
Comment 1 2011-06-28 08:10:46 PDT
Created attachment 98924 [details] testcase
Alexey Proskuryakov
Comment 2 2011-06-28 17:11:32 PDT
According to discussion in <https://bugzilla.mozilla.org/show_bug.cgi?id=433662>, WebKit behavior matches Hixie's reading of the spec. See also: bug 16867.
Glen Huang
Comment 3 2014-11-21 00:47:13 PST
The spec has changed https://dom.spec.whatwg.org/#concept-range-insert 10. If start and end are the same, set end to (parent, new offset). And lastest gecko and blink all follow through. I think webkit should do the same.
Lucas Forschler
Comment 4 2019-02-06 09:02:43 PST
Mass moving XML DOM bugs to the "DOM" Component.
Ahmad Saleem
Comment 5 2022-08-01 13:04:05 PDT
I am unable to reproduce this bug in Safari 15.6 on macOS 12.6 to get expected results. All browsers show two dialog matching with each other, where first dialog is 0,1 and then next is 0,0. It is same with Chrome Canary 106 and Firefox Nightly 105. It might be due to change in web-spec or other browsers aligned with Webkit or DOM3 superseded DOM2 behavior but since all browsers are same, I think we can mark it as "RESOLVED CONFIGURATION CHANGED". Thanks!
Note You need to log in before you can comment on or make changes to this bug.