Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-add FileReader.readAsBinaryString() ? #39

Closed
inexorabletash opened this issue Apr 21, 2016 · 2 comments
Closed

Re-add FileReader.readAsBinaryString() ? #39

inexorabletash opened this issue Apr 21, 2016 · 2 comments

Comments

@inexorabletash
Copy link
Member

Stats in Chrome: https://www.chromestatus.com/metrics/feature/timeline/popularity/814

Hovering around 0.0008% which is low. But an HTTPArchive search turned up thousands of uses; spot-checking, it's not just one library but several different uses. The method is implemented in Edge, FF, Chrome and Safari.

So... is it worth continuing to try and drop it from implementations, or should we just accept it as a wart on FileReader, document, and move on?

(As an aside, cribbing text() and arrayBuffer() from Body to Blob would be awesome...)

@annevk
Copy link
Member

annevk commented Apr 22, 2016

If it's implemented everywhere, yes, add it back. Not worth worrying about it.

Separate issue for text() and arrayBuffer()?

@gsnedders
Copy link

gsnedders commented May 27, 2016

Note Edge implemented it after it was dropped from the spec, so I presume they felt the pressure was strong enough to implement it regardless.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants