- From: Anne van Kesteren <notifications@github.com>
- Date: Thu, 27 Feb 2025 03:20:44 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 27 February 2025 11:20:48 UTC
@annevk 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-selection-range>composed selection range</dfn> is a
+<a>live range</a> that has an associated {{Range}} object, a
+<dfn export id=concept-legacy-selection-range for="composed selection range">legacy selection range</dfn>.</p>
Based on an email conversation I'm a bit less sure what the semantics of this range are. Say you have an element with a shadow root that contains the word "Test". The end user selects "es". `getSelection()` should not provide access to this shadow root, but apparently the set of changes proposed here do not enforce that. Or am I misunderstanding something?
--
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/pull/1342#discussion_r1973386577
You are receiving this because you are subscribed to this thread.
Message ID: <whatwg/dom/pull/1342/review/2647450415@github.com>
Received on Thursday, 27 February 2025 11:20:48 UTC