Re: New Progress draft (1.25)...

[Jonas Sicking]

Garrett Smith wrote:

On Fri, Oct 24, 2008 at 5:51 AM, Jonas Sicking [EMAIL PROTECTED] wrote:

Garrett Smith wrote:




I agree. Not sure if that is what you want to do before or after getting the
load/error/abort event though?

I should mention that I'm not particularly married to having things one way
or another. But I think we should have reasons for choosing.



Agree. Anyone who has another use case for loadend, please post up.


I was also wondering why in your use case it made sense to fire loadend 
before load/error/abort? I.e. what would you be doing in those events 
such that you want the progress bar hidden at that point.


Though I do agree that it makes sense to say i'm done before here's 
the data (or it failed).


/ Jonas

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

[Web Applications Working Group Issue Tracker]

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

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.