- From: Ryosuke Niwa <notifications@github.com>
- Date: Tue, 07 Mar 2023 13:55:10 -0800
- To: w3c/selection-api <selection-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 7 March 2023 21:55:22 UTC
> 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. So that it's consistent with the rest of selection APIs. If we ever wanted to add multi-range selection support, we don't want having to re-invent yet another API for that. > > 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. These two: https://github.com/WebKit/WebKit/blob/main/LayoutTests/fast/shadow-dom/selection-getComposedRanges.html https://github.com/WebKit/WebKit/blob/main/LayoutTests/fast/shadow-dom/selection-direction.html -- Reply to this email directly or view it on GitHub: https://github.com/w3c/selection-api/issues/161#issuecomment-1458926544 You are receiving this because you are subscribed to this thread. Message ID: <w3c/selection-api/issues/161/1458926544@github.com>
Received on Tuesday, 7 March 2023 21:55:22 UTC