Re: [w3c/selection-api] getComposedRange() review (Issue #161)

Other things worth tracking here:

* Perhaps we should still allow for multiple ranges API-wise and return a list. (And add a trailing s to the API name.)
* `StaticRange` has a concept of "valid" and this does not adhere to that. Perhaps we need a concept of "shadow-including valid" or at least point out that these ranges will not always be valid (but that's okay). Probably the latter until there's an actual use case.

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

Message ID: <w3c/selection-api/issues/161/1424609043@github.com>