Re: [w3c/selection-api] Support multi range selection (#41)

Right, I'm not claiming it preserves the selection for every DOM mutation you throw at it.  I'm just saying it's implemented and well defined in a spec.

I think your API hands over the complexity of mutations to the web developer and I don't think this is an edge case we can ignore - if they do mutations then the `start,end` offsets in the array are going to be wrong in many cases. I tend to think the UA is better positioned to deal with that. In my proposal, if a web developer **wants** to handle it for some reason they can just iterate the nodes non-destructively and save an array as in your proposal and then work from that.

-- 
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/41#issuecomment-289947715