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 01:50:00 +0200
To: "Ian Hickson" <ian@hixie.ch>
Cc: "WebApps WG" <public-webapps@w3.org>
Message-ID: <op.u10shmvjwxe0ny@widsith.local>
On Mon, 19 Oct 2009 00:08:38 +0200, Ian Hickson <ian@hixie.ch> wrote:

> On Sun, 18 Oct 2009, Charles McCathieNevile wrote:
>>
>> I propose to add the attributes totalItems and loadedItems to preogress
>> events, as a way of dealing with use cases like showing progress in
>> downloading an application cache. This allows for firing progress events
>> which have total/loaded values on individual items, by defining them as
>> referring to the current item in the presence of the totalItems /
>> loadedItems.
>>
>> Does that work for the use case?
>
> 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?)

cheers

Chaals

-- 
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 Sunday, 18 October 2009 23:50:38 GMT

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