Add definition for composed live range #1342
Conversation
There was a problem hiding this comment.
@smaug---- you should review this as well in due course. And @rniwa too I suspect.
dom.bs
Outdated
| <li><p>For each <a>composed live range</a> whose <a for=range>start node</a> is a | ||
| <a>shadow-including inclusive descendant</a> of <var>node</var>, set its <a for=range>start</a> to | ||
| (<var>parent</var>, <var>index</var>). | ||
|
|
||
| <li><p>For each <a>composed live range</a> whose <a for=range>end node</a> is an | ||
| <a>shadow-including inclusive descendant</a> of <var>node</var>, set its <a for=range>end</a> to | ||
| (<var>parent</var>, <var>index</var>). |
There was a problem hiding this comment.
This will need to be rebased once we land moveBefore().
However, I also think this needs to be reconciled with the "for each live range" above as we don't want to do duplicate work.
There was a problem hiding this comment.
Shouldn't this update the cached live range as well?
There was a problem hiding this comment.
The cached live range is covered by the existing "For each live range ..." rules. The cached live range is not composed and hence shouldn't consider for shadow-including inclusive descendant.
dom.bs
Outdated
| <p>A <dfn export id=concept-composed-live-range>composed live range</dfn> is a <a>live range</a> | ||
| that has one associated {{Range}} object - <dfn export | ||
| id=concept-composed-live-range-cached-live-range for="composed live range">cached live | ||
| range</dfn>.</p> |
There was a problem hiding this comment.
Why is this called cached live range?
There was a problem hiding this comment.
I wanted to give it a name so it doesn't get confusion between the "composed" live range and its associated "live range". Further, it is cached within the composed live range. I am open to naming suggestions.
dizhang168
force-pushed
the
composed-live-range
branch
from
54e6984 to
487cac0
Compare
As discussed at TPAC 2024, the specification for the new getComposedRanges() API need the introduction of the new definition "Composed live range" [1], which should react to mutations. This PR attempts to define that new concept. Once landed, we will add the spec language that uses composed live range in the Selection API. An overview of the spec changes necessary can be found at [2].
[1] w3c/selection-api#2 (comment)
[2] https://github.com/dizhang168/shadow-dom-selection/blob/main/selection-api-spec-changes.md
(See WHATWG Working Mode: Changes for more details.)
Preview | Diff