Re: [whatwg/dom] Add definition for composed selection range (PR #1342)

@dizhang168 commented on this pull request.



>       to <var>bp</var>.
 
+     <li>Otherwise, if <var>bp</var> is
+     <a for="boundary point">after</a> the
+     <var>range</var>'s <a for=range>end</a>, then:
+      <ol>
+       <li>Set <var>range</var>'s <a for=range>end</a>
+       to <var>bp</var>.
+
+       <li>If <var>selection range</var> is not null,
+       set <var>selection range</var>’s
+       <a for="range">end</a> to <var>bp</var>.

Right, in this example:
1. "legacy selection range" will collapse to {nodeInDifferentRootAfterCurrentEnd, 0}.
2. "composed selection range" will not collapse and will have its start node updated to {nodeInDifferentRootAfterCurrentEnd, 0}.
As you point out, start is now after end, but that is OK because Selection has the concept of anchor/focus. We can update getComposedRanges to use that instead.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/pull/1342#discussion_r1974164282
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/pull/1342/review/2648763459@github.com>