Re: [w3ctag/design-reviews] Modification of selection APIs to account for shadow dom (Issue #694)

Hi @mfreed7, we took another look today and we understand your reasoning and are happy with the proposal so we are going to close this.

One thing we wondered about: once this is implemented are there any remaining use cases for `getRangeAt()`? It seems that the new method covers all of them, and since it returns a static range it's more performant and less error-prone. If that assumption is correct, would it make sense to deprecate `getRangeAt()` and name the new method in a more generic way (e.g. `getRange()`)?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/694#issuecomment-1147664032
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/694/1147664032@github.com>