Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

readAsDataURL should be more precise about the data URL contents

Open
#104 5 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
html
Domain
documentation

Research direction

Start with the File API specification text for readAsDataURL and review the linked jsdom issue for the reported browser behavior. Compare the current description with how browsers encode Blob bytes and construct the data URL. Done means the specification states an exact, interoperable algorithm for the type attribute and Blob contents.

Written by the indexing model from the issue text.

Description

In particular, it appears all browsers base64-encode the contents; see https://github.com/jsdom/jsdom/issues/2269 for the original report.

Probably it'd be best to give the exact algorithm for creating the string from the contents of the type attribute and the bytes of the Blob.

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.