Disallow mutating state of Blob/File objects
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 118
- Forks
- 52
- Avg merge
- 9d 16h
- Merged PRs (30d)
- 1
Description
In particular, I think we should no longer add something like close() and make that an invariant of these objects.
That way there's no longer a need for defensive cloning (through serializing/deserializing) of these objects, which helps with https://github.com/whatwg/url/issues/277.
Making a note of this somewhere in the document seems sufficient.
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
Read the File API document sections defining Blob and File, then review the linked WHATWG URL issue for context. Done means the document explicitly records that these objects must not have mutable state and does not introduce a close() operation.
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