Re: [w3c/selection-api] Change Selection to be associated with a composed live range (PR #345)

johanneswilm left a comment (w3c/selection-api#345)

I wonder if the term "legacy selection range" makes sense. I gather we are not trying to deprecate these types of ranges. In the future, if we end up with even more range systems, we may end up with a large number of different "legacy" ranges that are still in use.  But that's just wording.

From the JS/author side of things, it would be of interest what is changing on the client side. There is no new API/method as far as I can tell. So what will the difference be? That ranges can now go across shadow root boundaries? Will this work with the existing getRange() method? 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/selection-api/pull/345#issuecomment-2718675621
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/selection-api/pull/345/c2718675621@github.com>