W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2011

[Bug 12596] <video> Explicitly state that preload=none fires a suspend event

From: <bugzilla@jessica.w3.org>
Date: Wed, 21 Sep 2011 20:22:40 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1R6TJY-0006tH-S7@jessica.w3.org>

--- Comment #11 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-09-21 20:22:39 UTC ---
> > This wouldn't work anyway. Why would "onclick" ever fire?
> It fires when the user clicks the video

Why would the user click the video? The UA might just start playing the video
when the user selects "play video" from the menu bar, or might start it when
the user says "start video" out loud, etc.

> The above script will break if the video has begun buffering before the video
> is clicked.

The above script will break in any number of ways because it makes a
fundamentally flawed assumption.

> > > A search engine that wants to index all media elements can just download and
> > > inspect them, it doesn't need to do so using a browser engine. 
> > 
> > It does if it wants to find the video resources embedded by script.
> Yes, but it can't actually index the video itself using a browser engine due to
> the cross-origin policy.

The script can't, but the indexer can. The indexer is the "browser engine" in
this context. It just wants the URLs. If a page is chaining videos one after
the other, a search engine that uses scripts would want to start each video it
comes across to see what happens when it gets to the end, for instance.

suspend="" is a hint. I don't really see how else it can be.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 21 September 2011 20:22:46 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:19 UTC