Need spec changes to Range and StaticRange to support nodes in different tree?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start with the linked StaticRange validity definition and the Range SetStart/SetEnd behavior, then trace how getComposedRanges() is specified across shadow boundaries. Done means the spec records an agreed, internally consistent treatment of cross-tree ranges and answers both questions raised here.
Written by the indexing model from the issue text.
Description
It's unclear to me about how we want to express allowing nodes across the shadow boundary for range in the spec.
The first example is StaticRange has a definition for valid, which specifies this StaticRange is invalid if nodes are in different tree. In the same time, getComposedRanges() would return invalid StaticRanges. Is this expected?
The second example is Range::SetStart and Range::SetEnd would collapse nodes to one point if they are in different trees. Shouldn't we also loose this requirement since we are supporting selection across the boundary?
- Dominant language
- HTML
- Stars
- 49
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from w3c/selection-api
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
w3c/selection-api#354 ·
-
Agenda+
Difficulty 3/5 1-2 days Newbie friendliness 48/100
w3c/selection-api#361 · 2 comments ·
-
w3c/selection-api#358 · 2 comments · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
w3c/selection-api#355 ·
-
the steps of Selection.extend() does not check whether the given offset is valid in the container Open
Difficulty 1/5 Under an hour Newbie friendliness 55/100
w3c/selection-api#353 · 1 comment ·
All issues in w3c/selection-api
Similar issues
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100