W3C home > Mailing lists > Public > public-webapi@w3.org > October 2007

Re: [progress-events] stalled - ISSUE-117

From: Charles McCathieNevile <chaals@opera.com>
Date: Sun, 28 Oct 2007 12:09:56 -0400
To: "Web API WG (public)" <public-webapi@w3.org>
Message-ID: <op.t0w0iuxnwxe0ny@widsith.local>

I propose to close ISSUE-117 by not including a stalled event.

See below for some more history...


A while ago, Hixie wrote...

On Tue, 31 Jul 2007, Charles McCathieNevile wrote:
> Maciej volunteered that
> > Somebody pointed out> > * HTML 5 has an event called "stalled" that is  
> dispatched after> > there are three seconds of no progress at all so you  
> do not have to> > create your own timer scripts.
> >> 3 seconds of no progress might not be out of the ordinary depending on 
> > connection speed and distance to the host. This seems pretty>  
> arbitrary.
>I agree with Maciej on this one. I raised ISSUE-117 for it, but my 
> proposal is that we do not adopt it (and that we point out to HTML-WG 
> that 3 seconds is very arbitrary). This would be consistent with how we 
> dealt with ISSUE-107...

To clarify -- in the HTML5 spec the three seconds is indeed arbitrary, the
spec just says "about three seconds" and it is expected that user agents
will adapt that as appropriate based on the connection speed, distance to
host, and so forth.

Furthermore, in the HTML5 case it's specifically for streaming multimedia,
where the user does care about a few seconds with no buffering going on
since it can mean that the media will skip.

I agree that it may well be inappropriate to have this event in the
progress events metaspecification. If it's included at all, it should
probably be listed as something that specifications should only include if
it is considered useful for that particular case.

Charles McCathieNevile  Opera Software, Standards Group
     je parle français -- hablo español -- jeg lærer norsk
http://my.opera.com/chaals              Try the Kestrel - Opera 9.5 alpha
Received on Sunday, 28 October 2007 16:10:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:24 UTC