W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2009

[whatwg] Restarting the media element resource fetch algorithm after "load" event

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 14 Oct 2009 21:20:59 +1300
Message-ID: <11e306600910140120w4683dc95qd8e59976dc5b24fc@mail.gmail.com>
On Wed, Oct 14, 2009 at 1:04 PM, Andrew Scherkus <scherkus at google.com>wrote:

> We use a combination of in-memory and block-based caching for media
> resources.  There is no guarantee whatsoever on what is loaded.  There's a
> nice side benefit of allowing complete random access to the file if the
> server supports range request (in my opinion a must if you're working on an
> audio/video site, but that's a side issue).


Indeed, we support that too.

For http:// we don't support load at all and never reach NETWORK_LOADED.
>  We're also baffled at what to report in our progress events because the
> numbers are seemingly useless in our context.  Sometimes we'll cache the end
> of the file to grab some useful metadata, but we don't want to fire a
> progress event saying we've loaded the last bit of the file...
>

We have the same issue, unsurprisingly. Currently our progress events are
not very useful because we report the download position (although we do
suppress progress events while we read metadata from the end of the file).
According to the spec, however, progress events should report the *amount*
of data downloaded, not the position within the resource. That's a bit more
useful, although it's still unclear what to do when data is discarded from
the cache and then re-downloaded.

Being the only browser (I think?) that doesn't fire the load event we've ran
> into site compatibility issues.  I believe a lot of web authors are used to
> tacking onload= into a tag and expecting it to work.  I've reached out to
> web authors to educate them about using canplaytype() +
> oncanplay/oncanplaythrough as alternatives to user agent checking and
> onload.
>

Good, thanks.

We plan to stop firing the "load" event in the next (and all future)
versions of Gecko, so we'll be doing that outreach too.

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
53:5-6]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20091014/a6327afa/attachment.htm>
Received on Wednesday, 14 October 2009 01:20:59 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:18 UTC