- From: <bugzilla@jessica.w3.org>
- Date: Wed, 07 Sep 2011 07:47:30 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12596 Philip Jägenstedt <philipj@opera.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #10 from Philip Jägenstedt <philipj@opera.com> 2011-09-07 07:47:27 UTC --- (In reply to comment #9) > (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? It fires when the user clicks the video: <video src=video.webm preload=none poster="playbutton.png"></video> The above script will break if the video has begun buffering before the video is clicked. Obviously, this can break for other reasons as well, but it's hard to see how the preload=none behavior could *not* become required for web compat. Waiting with spec'ing it until that has happened means that we can't actually pick a solution, we'll have to go with whatever some major browser decided on in the absence of a proper spec. > (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. Yes, but it can't actually index the video itself using a browser engine due to the cross-origin policy. If it's a modified browser engine in violation of the spec, I don't see how it's relevant to the discussion. -- 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, 7 September 2011 07:47:33 UTC