W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2008

[whatwg] Media elements delaying the load event.

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 18 Dec 2008 23:25:42 +1300
Message-ID: <11e306600812180225g1bc5f9aer785d09ad4fa81c84@mail.gmail.com>
On Thu, Dec 18, 2008 at 9:57 PM, Philip J?genstedt <philipj at opera.com>wrote:

> On Thu, 2008-12-18 at 14:41 +1300, Robert O'Callahan wrote:
> > Currently HTML5 does not require media elements to delay the load
> > event in any way. We certainly don't want to delay the load event
> > until the entire resource has finished loading (as we do for images),
> > but I think it would make sense to delay the load event until media
> > elements that are loading have reached the HAVE_CURRENT_DATA state (or
> > detected an error). This ensures intrinsic sizes are available so the
> > layout can stabilize, it ensures that scripts can access metadata, and
> > it ensures that the video is displaying something (if it's going to).
> Surely the load event should not be sent until the whole resource is
> loaded, otherwise it would clash rather severely with how progress
> events are defined. Is there some problem with holding the load event
> until the time when the resource is actually loaded?

Just to make it clear, I'm talking about media elements delaying the load
event for the enclosing HTML document:

"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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20081218/25c85832/attachment.htm>
Received on Thursday, 18 December 2008 02:25:42 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:46 UTC