On Dec 12, 2013, at 3:14 PM, Jonas Sicking wrote: > This does seem like an argument to create a asynchronous error rather than > throwing an exception though, since for form submission there would be no > place to throw an exception from.
Just to be clear, are you proposing an asynchronous error reported through an error event firing off of FileReader with a DOMError? Also, it isn't clear what fileListObject.files[0].close() would do for an asynchronous error, so perhaps both are necessary: treating it as "0 bytes" (empty byte sequence) *and* (where possible) using an asynchronous error reporting mechanism. -- A*
