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

> @mfreed7 : There are a few differences with that explainer. For starters, the method is called `getComposedRanges`, and returns a sequence of StaticRange objects. The `direction` property also returns "forward", "backward", or "none" to match selectionDirection property on the input element.

Interesting! Is there an issue discussing why `getComposedRanges()` plural, that returns a `[sequence]<StaticRange>` that seems to always just contain one `StaticRange`? I did really like the part of the new proposal that limited the API to a single range.


> Also, as part of the WebKit implementation, did you happen to write any WPTs?

Any comment on this one? I didn't see any tests, but wanted to double-check. We are interested in also implementing this API later this year, and WPTs would help to make sure we're interoperable.

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

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