W3C home > Mailing lists > Public > public-html@w3.org > June 2008

Re: ProgressEvent and unreachable networkState LOADED in HTMLMediaElement

From: Philip Jägenstedt <philipj@opera.com>
Date: Thu, 26 Jun 2008 18:46:31 +0700
To: HTML WG <public-html@w3.org>
Message-Id: <1214480791.10775.109.camel@localhost>

On Wed, 2008-06-25 at 16:51 +0700, Philip Jägenstedt wrote:
> This progress events draft states that exactly one of the events
> "error", "abort" and "load" must be dispatched. This is easy in most
> cases, but what about infinite media resources (streaming) or media
> resources so large that the browser can never cache the entire resource
> at once (certainly not in memory, and not on disk on devices either).

Rethinking this, it seems that it's as simple as triggering the abort
event when the element is eventually unloaded. Can/should this be
specified somewhere?

Still, it might be useful to note that the LOADED state might never be
reached for streaming or very large files. Thus, script authors should
never wait for the LOADED state to guarantee that the file can play
through, that's a guarantee that can never be given (CAN_PLAY_THROUGH is
the best guess we can give).

> Somewhat related, is the intention to have the "stalled" event added to
> the progress events spec?

I'm taking this to the WebApps WG as well.

-- 
Philip Jägenstedt
Opera Software
Received on Thursday, 26 June 2008 11:47:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:18 GMT