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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12596

--- Comment #9 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-09-06 06:48:04 UTC ---
(In reply to comment #7)
> 
> <video preload=none src=video.webm></video>
> <script>
> var v = document.querySelector('video');
> v.onclick = function() {
>   v.onloadedmetadata = function() {
>     // create UI using v.duration
>   };
>   v.play();
> };
> </script>

This wouldn't work anyway. Why would "onclick" ever fire?

(In reply to comment #8)
> 
> 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.


> This is pretty much the same situation as a user simply deciding to play a
> video, in which case it will start buffering. This will cause scripts to break
> if they don't expect that the user can play/pause a video that doesn't have
> (native or scripted) controls, but I don't think there's anything the spec can
> do about that.

Every <video> can have (and indeed should have) native controls, even those
that don't have the controls="" attribute. (If there's no controls=""
attribute, the controls will likely be in a context menu, rather than on-screen
controls.) The API is designed specifically to make it easy to create
controllers in script that interact with the browsers' native controls
coherently. This allows the user to still access advanced controls (e.g.
playback rate, captioning) even if the page doesn't provide full controls.


(Please reopen the bug if you respond, as I will not see comments otherwise
unless I happen to look at the bug for unrelated reasons.)

-- 
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 Tuesday, 6 September 2011 06:48:09 UTC