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

Well yeah, that could be bad, but it still wouldn't be any kind of leak unless the javascript code explicitly holds on to the created objects. And even then it's just bad javascript code, not a leak... Also (at least chrome) won't actually allocate these partial strings/arraybuffers unless javascript actually tries to access the result attribute (although I guess that might be observable somehow?)

But yeah, it definitely seems of limited usefulness to be able to inspect result before reading is complete.

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