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

It's definitely ambiguous in the current spec what result should return after calling a method but before the algorithm in the method sets result to something, so no matter what solution we pick the spec should be clarified.

I'm not sure what the supposed memory leak is though?

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

Received on Wednesday, 27 September 2017 23:13:00 UTC