On Sun, 26 Oct 2008 07:45:10 +1100, Web Applications Working Group Issue
Tracker <sysbot+trac...@w3.org> wrote:
ISSUE-78: HTML5 stalled and suspend progress events [Progress Events]
Closed, by adding these events to the spec as things that conformant specs
may use (and should, if they are going to provide such functionality).
cheers
Chaals
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
These should be added to the draft, I suggest the following 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.
--
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
