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: Charles McCathieNevile <chaals@opera.com>
Date: Fri, 31 Oct 2008 16:05:35 +0100
To: "Web Applications Working Group WG" <public-webapps@w3.org>
Cc: "public-svg-wg@w3.org" <public-svg-wg@w3.org>
Message-ID: <op.ujv9jlv1wxe0ny@widsith.local>

Cc'ed to SVG as well, since people there use progress events. Please reply  
to the Web Apps group (reply-to is set).

On Sat, 25 Oct 2008 22:45:10 +0200, Web Applications Working Group Issue  
Tracker <sysbot+tracker@w3.org> wrote:

> ISSUE-78: HTML5 stalled and suspend progress events [Progress Events]
>
> http://www.w3.org/2008/webapps/track/issues/78
>
> Raised by: Philip Jägenstedt
> On product: Progress Events
>
> http://www.w3.org/html/wg/html5/#mediaevents
>
> The events in HTML 5 fired for the media elements (<video>+<audio>) are  
> called ProgressEvents and are intended to eventually refer to the  
> Progress Events spec.
>
> Currently the HTML5 draft specifies two events not covered by the  
> Progress Events draft: stalled and suspend

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?

> These should be added to the draft, I suggest the following phrasing:

If we add these, I like the suggested phrasing.

> Name / Description / How often? / When?
>
> stalled / The operation is unexpectedly not progressing / zero or more /  
> May be dispatched zero or more times after a loadstart event, before any  
> error, abort or load event is dispatched
>
> suspend / The operation is temporarily suspended / zero or more / May be  
> dispatched zero or more times after a loadstart event, before any error,  
> abort or load event is dispatched
>
> Rationale:
>
> Stalled is used to signal that the download is for some reason not  
> progressing, but the user agent has not yet given up and fired an error  
> event. In HTML5 this happens when no data has been received for  
> approximately 3 seconds.
>
> Suspend is used to signal that the user agent is deliberately pausing  
> the download. In the case of audio/video, the user agent may initially  
> download only a portion of the file and fetch the rest only when/if the  
> user plays the audio/video to a point where it is needed.

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 Friday, 31 October 2008 15:06:10 GMT

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