Lenas wrote:
Keep in mind that most embeds are HTML5, not Flash.
The key word being "most". The old [yt] tag def explicitly embedded a Flash object whether you liked it or not. You'd get flash embedding even if you were opted into Youtube's HTML5 trial. The new tags don't have this problem because they don't actually embed anything. They just fetch a URL in an <iframe>, letting YouTube/Vimeo decide how they want to embed it.
If you try it, you'll see that embedded YouTube videos on the Glade now respect your settings if you've opted in to the HTML5 test.
Which reminds me, you should all do this if you haven't yet:
http://www.youtube.com/html5
Pages with lots of videos (earbug thread, etc.) load much faster with HTML5.Ok, slight caveat: full screen mode doesn't work with HTML5 embedding just yet. Apparently this is a browser limitation.
Addendum #2: And yet oddly enough Vimeo's fullscreen
does work with HTML5 embedding, even though they claim it doesn't.
Aizle wrote:
For the record. Yuck. Why fix what wasn't broken?
I'm not quite sure what you mean by "Yuck". The old tags were pretty clunky if not outright broken. YouTube doesn't have a stable URL scheme. That's the whole reason they introduced the youtu.be shortener. The old [yt] tags would barf unless the v={whatever} parameter was the first getvar in the URL. This often meant having to edit it by hand before you could use it on the Glade. The new tags vastly simplify things. They also bring the Glade into compliance with YouTube's intended URL scheme for sharing videos. It might not matter now, but it's a good move in terms of future-proofing.