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

> I'm not sure that changing the definition of "valid" would be correct. We'd have to look at the callers. We might well need valid and shadow-including valid as separate concepts.

The only web API that I can find that returns a StaticRange is https://w3c.github.io/input-events/#dom-inputevent-gettargetranges. Do you know of others?

> It's also not clear to me we can just change the public API of `Range`. That seems quite dangerous.

I think the proposal is to only change the public API of `StaticRange`, and not `Range`, right? I'd agree that we don't want to change what `Range` returns, or it will likely not be web compatible.

Perhaps your comment was about this part of the comment?

> The same logic should also be applied for Range setEnd/setStart.

But that just refers to this behavior: https://github.com/mfreed7/shadow-dom-selection?tab=readme-ov-file#changes-to-existing-selection-apis

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

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