We should have more steps for Selection#extend()
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 202
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
We should describe following situation explicitly:
- Call Selection#extend() with (null, int);
which one, throw, ignore or removeAllRanges()? - Call Selection#extend() when Seleciton#type is "None"
which one throw, ignore, or collapse()? - Throw IndexSizeError for invalid offset
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.
Research direction
Start with the Selection#extend() specification and review the three cases listed in the issue: null with an integer, a selection whose type is "None", and an invalid offset. Define and document the expected behavior for each case, including when IndexSizeError is thrown, so the Selection API steps are explicit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100