[w3c/selection-api] Need spec changes to Range and StaticRange to support nodes in different tree? (Issue #169)

It's unclear to me about how we want to express allowing nodes across the shadow boundary for `range` in the spec. 

The first example is [StaticRange](https://dom.spec.whatwg.org/#staticrange-valid) has a definition for **valid**, which specifies this StaticRange is invalid if nodes are in different tree. In the same time, `getComposedRanges()` would return invalid StaticRanges. Is this expected? 

The second example is `Range::SetStart` and `Range::SetEnd` would collapse nodes to one point if they are in different trees. Shouldn't we also loose this requirement since we are supporting selection across the boundary?    

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

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