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

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

From: Anne van Kesteren <annevk@opera.com>
Date: Fri, 02 Mar 2012 08:09:36 +0100
To: "Arun Ranganathan" <aranganathan@mozilla.com>, "Eric U" <ericu@google.com>
Cc: "Web Applications Working Group WG" <public-webapps@w3.org>, "Jonas Sicking" <jonas@sicking.cc>
Message-ID: <op.wai7iaog64w2qv@annevk-macbookpro.local>
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 van Kesteren
Received on Friday, 2 March 2012 07:10:05 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:38 UTC