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

In the last draft, ```collapse()``` ```extend()``` ```setBaseAndExtent()``` and ```selectAllChildren()``` reject nodes in a different root though ```addRange()``` accepts anything.  It's inconsistent.  IMO, ```addRange()``` should reject Ranges with nodes in different roots.

The Background section of the draft says:

> IE9 and Firefox 6.0a2 allow arbitrary ranges in the selection, which follows what this spec originally said. However, this leads to unpleasant corner cases that authors, implementers, and spec writers all have to deal with, and they don't make any real sense.



-- 
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-280029132