Set FileReader.error to an AbortError when abort() is called.
Open
Nobody has claimed this yet.
feature request
- Dominant language
- HTML
- Stars
- 118
- Forks
- 52
- Avg merge
- 9d 16h
- Merged PRs (30d)
- 1
Description
All implementations seem to already do this, yet the spec currently seems to say that error should remain null if abort() is called. Probably easiest to just change the spec to set error to an AbortError.
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 by locating the File API specification text governing FileReader.abort() and its error state. Update the stated behavior so abort() sets error to AbortError, then check the surrounding abort algorithm for consistency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100