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

2012-03-03 Thread Anne van Kesteren
On Fri, 02 Mar 2012 23:31:38 +0100, Eric U wrote: On Thu, Mar 1, 2012 at 11:09 PM, Anne van Kesteren wrote: 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. Pardon my ignorance, but why not?

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

2012-03-02 Thread Arun Ranganathan
Eric, > On Fri, 02 Mar 2012 01:01:55 +0100, Eric U wrote: > > On Thu, Mar 1, 2012 at 3:16 PM, Arun Ranganathan > > 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* meth

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

2012-03-02 Thread Eric U
On Thu, Mar 1, 2012 at 11:09 PM, Anne van Kesteren wrote: > On Fri, 02 Mar 2012 01:01:55 +0100, Eric U wrote: >> >> On Thu, Mar 1, 2012 at 3:16 PM, Arun Ranganathan >> wrote: >>> >>> OK, so the change is to ensure that these events are fired directly, and >>> not queued, right?  I'll make this c

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

2012-03-01 Thread Anne van Kesteren
On Fri, 02 Mar 2012 01:01:55 +0100, Eric U wrote: On Thu, Mar 1, 2012 at 3:16 PM, Arun Ranganathan 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

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

2012-03-01 Thread Eric U
On Thu, Mar 1, 2012 at 3:16 PM, Arun Ranganathan wrote: > Eric, > >> In the readAsText in the latest draft [1] I see that readyState gets >> set to done "When the blob has been read into memory fully". >> I see that elsewhere in the progress notification description, "When >> the data from the blo

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

2012-03-01 Thread Arun Ranganathan
Eric, > In the readAsText in the latest draft [1] I see that readyState gets > set to done "When the blob has been read into memory fully". > I see that elsewhere in the progress notification description, "When > the data from the blob has been completely read into memory, queue a > task to fire a

[fileapi] timing of readyState changes vs. events

2012-02-29 Thread Eric U
In the readAsText in the latest draft [1] I see that readyState gets set to done "When the blob has been read into memory fully". I see that elsewhere in the progress notification description, "When the data from the blob has been completely read into memory, queue a task to fire a progress event c