W3C home > Mailing lists > Public > public-webapi@w3.org > April 2007

Re: progress events and error

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 24 Apr 2007 12:01:52 -0700
Message-ID: <462E5420.8060300@sicking.cc>
To: Charles McCathieNevile <chaals@opera.com>, Web APIs WG <public-webapi@w3.org>

Charles McCathieNevile wrote:
> On Tue, 24 Apr 2007 08:25:58 +0200, Anne van Kesteren <annevk@opera.com> wrote:
> 
>> On Mon, 23 Apr 2007 14:44:53 +0200, Jonas Sicking <jonas@sicking.cc> wrote:
>>> [...]
>>>
>>>> I think you do want at least one loadstart and progress event before
>>>> that event though.
>>> Why? ('that event' means the error event here, right?)
>> http://www.w3.org/mid/8FDB961A-31D4-40CB-BFC9-0CE780CD20AB@apple.com
> 
> As I read that message (then and now) it was to clarify that Maciej felt we need a loadstart and some end condition event, and couldn't overload progress to perform those functions. I didn't interpret it to mean that you need the actual progress event to fire (and Maciej allows for this explicitly in the message).
> 
> So as I understand it the current spec matches what Maciej was asking for.

Ah, I missed that progress could be fired zero times before error. 
That's good. Thinking about it some more it does make sense that if we 
successfully start the load and return from whatever call initiated the 
load that we demand that loadstart is the first thing that is fired always.

/ Jonas
Received on Tuesday, 24 April 2007 19:03:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:57 GMT