[w3c/selection-api] Selection should detach associated Range when Range move to another root. (#79)

Current Selection API should specify behavior when associate Range, added by Selection#addRange(), when it is moved to another document or it is moved DocumentFragment.

As of February 2017, Both Edge and Firefox keep such Range to associated. They returns node in another document by Selection#anchorNode and focusNode properties.

I propose when associated Range is moved another root, Selection should stop to associate it.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/selection-api/issues/79

Received on Monday, 13 February 2017 06:08:44 UTC