- From: Sean Feng <notifications@github.com>
- Date: Thu, 27 Feb 2025 10:39:37 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 27 February 2025 18:39:41 UTC
@sefeng211 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>. I read the updated algorithm won't collapse the example given Dominic (`getSelectionRange.getRangeAt(0).setStart(nodeInDifferentRootAfterCurrentEnd, 0)`) because the nodes are still in the same document, am I missing something? So now the `start node` of the `composed selection range` is after the `end node` of it? -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/pull/1342#discussion_r1974149010 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/pull/1342/review/2648737754@github.com>
Received on Thursday, 27 February 2025 18:39:41 UTC