W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2012

Re: [fileapi] timing of readyState changes vs. events

From: Arun Ranganathan <aranganathan@mozilla.com>
Date: Fri, 2 Mar 2012 15:26:09 -0800 (PST)
To: Anne van Kesteren <annevk@opera.com>
Cc: Web Applications Working Group WG <public-webapps@w3.org>, Jonas Sicking <jonas@sicking.cc>, Eric U <ericu@google.com>
Message-ID: <1337501889.4209560.1330730769649.JavaMail.root@zimbra1.shared.sjc1.mozilla.com>
Eric,

> On Fri, 02 Mar 2012 01:01:55 +0100, Eric U <ericu@google.com> wrote:
> > On Thu, Mar 1, 2012 at 3:16 PM, Arun Ranganathan
> > <aranganathan@mozilla.com> wrote:
> >> OK, so the change is to ensure that these events are fired
> >> directly,
> >> and not queued, right?  I'll make this change.  This applies to
> >> all
> >> readAs* methods.
> >
> > Yup.  It should apply to any event associated with a state change
> > [so
> > e.g. onload, but not onloadend].
> 
> Uhm. What you need to do is queue a task that changes the state and
> fires
> the event. You cannot just fire an event from asynchronous
> operations.


Anne's right (asynchronous operations happen on the event queue).

I think the same task can change state and fire the event.  This may take care of the timing issue.

-- A*
Received on Friday, 2 March 2012 23:26:38 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:50 GMT