Re: [w3c/selection-api] Specify the behavior when DOM mutation occurs across shadow-crossing selection (Issue #168)

<details><summary>Editing WG Nov 14, 2024 IRC notes: Specify composed range and mutation behavior in DOM spec</summary>

08:20 <whsieh> next issue: https://github.com/w3c/selection-api/issues/168
08:21 <whsieh> Di: how do DOM mutations affect compose ranges? see slide 6 above
08:22 <whsieh> Di: if we use current definition in the DOM spec, there would not be any change in the live range
08:22 <whsieh> Di: however, if we were to use composed ranges, it would need to change
08:22 <whsieh> Di: both blink and gecko don't care about shadow inclusiveness
08:23 <whsieh> dandclark: seems straightforward enough to patch the spec to be shadow inclusive
08:24 <whsieh> whsieh what about multi-range selections?
08:25 <whsieh> Di: generalizes to multiple ranges
08:25 <whsieh> resolve: define composed range mutations in the DOM spec
08:26 <whsieh> Di: check with other folks how are not in the meeting (sanket + smaug)
08:27 <whsieh> mfreed: next step — make a spec PR?
</details>

Update DOM spec by adding details for composed range
For example:

> To remove a [node](https://dom.spec.whatwg.org/#concept-node) node, with an optional suppress observers flag, run these steps:
> ...
> 4. For each [live range](https://dom.spec.whatwg.org/#concept-live-range) whose [start node](https://dom.spec.whatwg.org/#concept-range-start-node) is an [inclusive descendant](https://dom.spec.whatwg.org/#concept-tree-inclusive-descendant) of node, set its [start](https://dom.spec.whatwg.org/#concept-range-start) to (parent, index).

Add: For each composed range whose start node is a shadow-inclusive descendant of node, set its start to (parent, index).

We could also refactor the DOM specification with a new “Update Selection” algorithm.

@annevk @sanketj @smaug---- for reference

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

Message ID: <w3c/selection-api/issues/168/2476928037@github.com>