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

Actually, the spec already sort of implies that result shouldn't be available until LOAD time. All the various read method algorithms don't assign any value to `result` until the "process read EOF" steps. It's probably still a good idea to write some tests to figure out what browsers are actually doing here though (for example does `result` keep the result of a previous read operation until a new load has finished, or is it reset back to null when the new read starts?)

And I added the use counter to chrome to see how often this (non-spec-compliant) behavior of returning result before load is finished is actually triggered.

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