W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2009

Re: Using progress events for other purposes

From: Charles McCathieNevile <chaals@opera.com>
Date: Mon, 19 Oct 2009 06:05:47 +0200
To: "Simon Pieters" <simonp@opera.com>, "Ian Hickson" <ian@hixie.ch>
Cc: "WebApps WG" <public-webapps@w3.org>
Message-ID: <op.u104bxk0wxe0ny@widsith.local>
On Mon, 19 Oct 2009 05:20:49 +0200, Simon Pieters <simonp@opera.com> wrote:

> On Mon, 19 Oct 2009 01:50:00 +0200, Charles McCathieNevile  
> <chaals@opera.com> wrote:
>>> That would work for appcache, yeah. We'd need to make sure the spec was
>>> clear about what the other attributes should be set to in this  
>>> situation,
>>> too, since in appcache they is only one event per file.
>> OK, I'll work on it to try and get an editor's draft out tomorrow. My  
>> rough idea is that you can send an event which has lengthComputable  
>> false and totalItems / loadedItems, and IFF they have lengthComputable  
>> true then the loaded and total refer to the particular item - (does  
>> itemCount start  from zero or one?)
> Isn't itemCount redundant with loadedItems?

Yep - it is what I was thinking of calling loadedItems before, and snuck  
back into my brain. (I prefer the loadedItems / totalItems names because  
they match the loaded/total attributes, and because they go very well with  
the 70s-style ribbons in the spokes of my bike wheels).



Charles McCathieNevile  Opera Software, Standards Group
     je parle français -- hablo español -- jeg lærer norsk
http://my.opera.com/chaals       Try Opera: http://www.opera.com
Received on Monday, 19 October 2009 04:06:27 UTC

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