Re: [w3c/selection-api] Specify the behavior when DOM mutation occurs across shadow-crossing selection (Issue #168)

> Seems like that operation (manipulation of a live range) should go through the same "update selection" algorithm which should take care of the details.

That would mean we have multiple ranges associated with the selection representing the same conceptual range within the selection.

Maybe instead the "public selection live range" (`getRange(0)`) should point directly to the selection live range and update that, which then updates the selection. With multiple ranges that would still work, with each selection live range having its own public selection live range.

The most difficult part here is probably defining the "selection live range".

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

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