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

[whatwg] HTMLMediaElement load and autoplay

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 8 Jul 2008 23:03:25 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0807082302010.11215@hixie.dreamhostps.com>
On Thu, 3 Jul 2008, Philip J?genstedt wrote:
> 
> OK, so in that case I suppose the requirement is to call load() sometime 
> during the parsing phase. This probably implies that the loadstart event 
> must be fired on all media elements before the load event is fired on 
> the owner document.

Yes, typically.


> As a side note, we certainly can't want to wait for all media elements 
> to fire the load before firing it on the parent document event as that 
> may take several minutes or never happen at all -- breaking half of the 
> web that relies on this behavior.

Right; the spec says only things that "delay the load event" delay the 
load event, and <video> isn't one of them.


> > The script can tell if the download is being blocked by checking 
> > bufferingThrottled and bufferingRate. I'm not sure we want a way to 
> > override the blocking since it is supposed to represent user intent.
> 
> Indeed, but it wouldn't be a spec violation to value automatic loads and 
> script-invoked loads slightly different internally. That said, it's not 
> a priority and I will reraise the question if it appears to be a real 
> need in the future.

Ok.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 8 July 2008 16:03:25 UTC

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