Re: [w3c/selection-api] Clarify association between a selection and its range (#2)

Adding Agenda+ for this issue. The goal is to add definitions and spec so we can support composed ranges and refer to those definitions in the Selection API spec. To summarize the suggested changes:

## 1. Redefine a live range:

Before: Objects implementing the [Range](https://dom.spec.whatwg.org/#range) interface are [live ranges](https://dom.spec.whatwg.org/#concept-live-range).

After: A live range is a [range](https://dom.spec.whatwg.org/#concept-range) that is affected by mutations to the [node tree](https://dom.spec.whatwg.org/#concept-node-tree). Objects implementing the [Range](https://dom.spec.whatwg.org/#range) interface are live ranges.

## 2. Add new Composed live range definition

A composed live range is a live range that has one associated [Range](https://dom.spec.whatwg.org/#range) object cached range.

## 3. Change "remove a node" mutation

Change the "remove a node" mutation algorithm to account for composed live range by finding descendant nodes using shadow-including inclusive traversal.

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

Message ID: <w3c/selection-api/issues/2/2593490329@github.com>