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

Re: ISSUE-78: HTML5 stalled and suspend progress events [Progress Events]

From: Ian Hickson <ian@hixie.ch>
Date: Fri, 31 Oct 2008 18:31:50 +0000 (UTC)
To: Web Applications Working Group WG <public-webapps@w3.org>
Message-ID: <Pine.LNX.4.62.0810311830010.1041@hixie.dreamhostps.com>

On Fri, 31 Oct 2008, Charles McCathieNevile wrote:
> We have previously discussed a stalled event, in the context of 
> suggested timing for producing progress events. We decided not to set a 
> specific timing, because the use cases vary a lot and so the appropriate 
> timing of progress events does too. So we could add the event directly 
> to this spec, as a convenience.
> I think the suspend event would be useful and am inclined to add it. 
> Should there be an unsuspend event, or is it enough to just emit a new 
> progress event signifying taht something started again? And do others 
> think this is a useful addition or just extra work?

I don't think 'unsuspend' is that useful given that you can just detect 
'progress'. I do think that including all the events specs invent that use 
ProgressEvents into the progress spec makes sense, since that way other 
specs will reuse them. I still don't think ProgressEvents should really 
have (nor really can have) much in the way of normative text, so I don't 
think that it's really complicated to add events.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 31 October 2008 18:32:27 UTC

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