w3c / w3c/FileAPI

revokeObjectURL does not error check URL parsing and passes string to "remove an entry"

Open Beginner friendly
#207 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Spotted two minor issues in revokeObjectURL

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.

Research direction

Start with the revokeObjectURL algorithm in the linked File API specification and compare its URL parsing and Blob URL Store steps with the linked remove-an-entry definition. Done means the algorithm handles URL parsing errors and passes the parsed urlRecord to the removal step.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.