- From: Jonas Sicking <jonas@sicking.cc>
- Date: Tue, 7 Jun 2011 14:04:55 -0700
- To: Jian Li <jianli@chromium.org>
- Cc: "arun@mozilla.com" <arun@mozilla.com>, Web Applications Working Group WG <public-webapps@w3.org>
On Tue, Jun 7, 2011 at 11:51 AM, Jian Li <jianli@chromium.org> wrote: > > > On Tue, Jun 7, 2011 at 11:23 AM, Jonas Sicking <jonas@sicking.cc> wrote: >> >> On Tue, Jun 7, 2011 at 10:43 AM, Jian Li <jianli@chromium.org> wrote: >> > I have a couple questions regarding abort behavior. >> > >> > If the reading is completed and the loadend event has been fired, do we >> > want >> > to fire loadend event again when abort() method is called? >> >> No >> >> > Do we want to reset error to null or leave it intact when abort() method >> > is >> > called? >> >> If called after load/abort/error has fired the calling abort() should >> just throw an exception and not alter the FileReader object in any >> way. > > Do you mean we should throw if abort() is called after load/abort/error has > been fired but before loadend event has been fired? Yes. > If so, what kind of exception should we throw? I need to get updated on the status on various exceptions, so I don't have an opinion on this at this time. > The spec only mentions that "If readyState = DONE set result to null." I actually disagree with that sentence. / Jonas
Received on Tuesday, 7 June 2011 21:06:00 UTC