- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 19 Aug 2009 05:50:04 +0000 (UTC)
- To: Anne van Kesteren <annevk@opera.com>
- Cc: public-webapps@w3.org
On Tue, 18 Aug 2009, Anne van Kesteren wrote: > On Tue, 18 Aug 2009 00:38:49 +0200, Ian Hickson <ian@hixie.ch> 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. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 19 August 2009 05:50:39 UTC