On 5/23/11 6:14 PM, Arun Ranganathan wrote:
On 5/23/11 1:20 PM, Kyle Huey wrote:
To close the loop a bit here, Firefox 6 will make the change to
FileReader.abort()'s throwing behavior agreed upon here.
(https://bugzilla.mozilla.org/show_bug.cgi?id=657964)
We have not changed the timing of the events, which are still
dispatched synchronously.
The editor's draft presently does nothing when readyState is EMPTY,
but if readyState is DONE it is specified to set result to null and
fire events (but flush any pending tasks that are queued).
http://dev.w3.org/2006/webapi/FileAPI/#dfn-abort
Also note that we're NOT firing *both* error and abort; we should only
fire abort, and *not* error.
I should change the spec. to throw. Eric, you might change the spec.
(and Chrome) to NOT fire error and abort events :)
Sorry, to be a bit clearer: I'm talking about Eric changing
http://dev.w3.org/2009/dap/file-system/file-writer.html#widl-FileSaver-abort-void
to match http://dev.w3.org/2006/webapi/FileAPI/#dfn-abort
-- A*
