Re: Using progress events for other purposes

On Wed, 19 Aug 2009 07:50:04 +0200, Ian Hickson <> wrote:

> On Tue, 18 Aug 2009, Anne van Kesteren wrote:
>> On Tue, 18 Aug 2009 00:38:49 +0200, Ian Hickson <> wrote:
>> > The Application Cache feature in HTML5 uses an event named 'progress'
>> > as part of the process, in a manner mostly unrelated to the rest of
>> > the progress events feature. It needs two values of context
>> > information (number of files being downloaded, number of files
>> > obtained so far). Should I just reuse the ProgressEvents interface? It
>> > seems that doing so is a violation of the Progress Events
>> > specification, but I don't see why it should be.
>> If we extend the ProgressEvent interface in the future we'd have to
>> consider non-byte-length-based uses of it. Is that really a good idea?
>> (I suppose that could be a different interface that extends
>> ProgressEvent, but still.)
> If implementors would rather I made up a new interface that was nearly
> identical to ProgressEvent and used that, I can do that too.

The alternative is to think now about extending Progress Events to deal  
with non byte-length progress (e.g. a series of transactions, each of  
which is very rapid alone but which add up to minutes).

My preference would be to create new attributes for this case rather than  
overload the total/loaded attributes. A third approach would be to have a  
flag which specifies whether the total/loaded attributes measure bytes,  
and a related fourth would be to have an attribute that says what the  
total/loaded attributes are measuring.

I have raised ISSUE-105 for this question.



Charles McCathieNevile  Opera Software, Standards Group
     je parle français -- hablo español -- jeg lærer norsk       Try Opera:

Received on Sunday, 27 September 2009 18:00:01 UTC