On Thursday, July 07, 2011 10:21 PM, Arun Ranganathan wrote:
On 7/6/11 10:13 PM, Cameron McCormack wrote:
There was a recent change in Web IDL which made interface types (like
the readAsXXX argument types) not include null by default, and if you
want to allow null, to write it as “Type?”.
On 7/6/11 10:13 PM, Cameron McCormack wrote:
Hi Arun,
Adrian Bateman:
The spec doesn't seem to state this explicitly and I can't tell if
there is supposed to be an implicit requirement from WebIDL. Perhaps
the expectation is that this falls into the error condition and
should set readyState to
http://dev.w3.org/2006/webapi/FileAPI/#reading-a-file
What is the expected behaviour for FileReader.readAsXXX(null)? Currently
I think both IE10 and Chrome fail silently and there are no events fired
whereas Firefox appears to throw an internal NS_ERROR_INVALID_POINTER
exception.
The spec
On 7/6/11 7:54 PM, Adrian Bateman wrote:
http://dev.w3.org/2006/webapi/FileAPI/#reading-a-file
What is the expected behaviour for FileReader.readAsXXX(null)? Currently
I think both IE10 and Chrome fail silently and there are no events fired
whereas Firefox appears to throw an internal
Hi Arun,
Adrian Bateman:
The spec doesn't seem to state this explicitly and I can't tell if
there is supposed to be an implicit requirement from WebIDL. Perhaps
the expectation is that this falls into the error condition and
should set readyState to DONE, result to null, and process the
