Re: [w3c/selection-api] Clarify association between a selection and its range (#2)

I don't think we need any new IDL at this stage.

A live composed range is an internal concept, though it would require many of the things that a live range has, just none of the public API. But we would have to update it after tree mutations, for instance. A live composed range also has a pointer to a `Selection` object, to forward mutations.

A `Selection` object points to a live composed range and also forwards mutations.

The live range from `getRangeAt(0)` can initially be computed from the live composed range. Though once it's out there we'd also have to maintain it in parallel, requiring yet more pointers and forwarding of operations.

Having said that, what is an internal concept of composed anchor/focus?

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

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