I am cloning a DOM range using the ClonanRange () function. If I then modify the original range object like this:
range.setStart (range.startContainer, 1); The clone preserves the old startoffset as expected However, if I modify the DOM tree, the clone startoffset will also be affected. Is there a deliberate internal wiring between the Dom Tree and all the categories related to it (including the clone)?
Yes, there is boundaries under DOM mutation it happens? Recently it specifies under this section (thanks to Robbie paying attention to it).
Comments
Post a Comment