According to the spec the result attribute of FileReader should not be assigned until just before the `load` event is fired. In particular for all progress events result should return null.

Other browsers seem to already do this, so maybe changing chrome would be safe. A use counter has been added to figure out how often websites actually access result while a load is in progress.

See also https://github.com/w3c/FileAPI/issues/79