readAsDataURL should be more precise about the data URL contents
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 118
- Forks
- 52
- Avg merge
- 9d 16h
- Merged PRs (30d)
- 1
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.
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 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.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100