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

Otherwise you get a giant memory leak. Reportedly Firefox already does this. Chrome allocates strings/buffers and will quickly get slow.

-- 
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

Received on Thursday, 4 May 2017 13:31:40 UTC