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

>  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

@rniwa Any plan to merge them into WPT? Probably as tentative? 

> Interesting! Is there an issue discussing why getComposedRanges() plural, that returns a [sequence]<StaticRange> that seems to always just contain one StaticRange?

Also it simplifies Gecko's implementation since we probably need to make them able to return multiple ranges.  


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

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