Disallow mutating state of Blob/File objects

Open
#75 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
html
Domain
documentation

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.

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.

Dominant language
HTML
Stars
118
Forks
52
Avg merge
9d 16h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from w3c/FileAPI

All issues in w3c/FileAPI

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.