- From: Dominic Farolino <notifications@github.com>
- Date: Tue, 28 Jan 2025 07:48:37 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 28 January 2025 15:48:41 UTC
@domfarolino commented on this pull request.
>
<p class=note>Algorithms that modify a <a>tree</a> (in particular the <a for=/>insert</a>,
<a for=/>remove</a>, <a>replace data</a>, and <a lt="split a Text node">split</a> algorithms) modify
-<a>live ranges</a> associated with that <a>tree</a>.
+<a>live ranges</a> associated with that <a>tree</a>.</p>
+
+<p>A <dfn export id=concept-composed-live-range>composed live range</dfn> is a <a>live range</a>
+that has one associated {{Range}} object - <dfn export
+id=concept-composed-live-range-cached-live-range for="composed live range">cached live
+range</dfn>.</p>
I think "legacy selection range" sounds good, to make clear that it's only maintained for behavior expected by the Selection API. I might also go further and rename "composed live range" to "composed selection range" or something, to also indicate that this concept only exists for Selection API purposes.. thoughts?
--
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/pull/1342#discussion_r1932419420
You are receiving this because you are subscribed to this thread.
Message ID: <whatwg/dom/pull/1342/review/2578693613@github.com>
Received on Tuesday, 28 January 2025 15:48:41 UTC