Re: [w3c/FileAPI] Don't update FileReader's result until "LOAD" (#79)

We could provide incremental updates for arraybuffers by allocating `new ArrayBuffer(file.size)` as soon as `readAsArrayBuffer` is called, then update the buffer for each progress event. This would avoid the performance issues Chrome is hitting.

Unfortunately it means that `reader.result.byteLength` will not reflect progress, which may be considered a backwards incompatible change.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/issues/79#issuecomment-299186671