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

I don't think changing the behavior of `Selection`-`Range` relationship like that only in the case where a Range's boundary points is in another document or otherwise disconnected is a good idea. This makes the API's behavior rather hard to predict.

We should either spec Gecko/Edge's behavior or what WebKit does, which is that `addRange` doesn't let the original range control selection, and `getRangeAt` makes a new `Range` each time it gets called.

-- 
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#issuecomment-279498976