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

[WCCG had their spring F2F](https://github.com/WICG/webcomponents/issues/978#issuecomment-1516897276) in which this was discussed. Present members of WCCG identifiers that there are several issues to resolve:

 - The behavior of DOM mutations needs to be specified. For example, if the selection ends within light dom content that is slotted, and that content is removed, where is the new endpoint of the “true range”?
 - There are still open questions around support of multiple ranges

There was also a resolution to open two new issues to discuss further details; #163 and #164 have been opened.



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

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