Google Chrome gets HTML video support
Google's Matthew Papakipos touted HTML 5 features including the video tag at the Google I/O conference Wednesday.
(Credit: Stephen Shankland/CNET)Google has begun supporting a new HTML feature to show video in its Chrome browser as an alternative to Adobe Systems' much more widely used Flash, but the technology overall remains rough around the edges.
The support comes in Chrome 3.0.182.2, a developer preview version that on Wednesday inaugurated work on the 3.0 generation of the Google browser. HTML video is one of a handful of technologies in the still unfinalized HTML 5 standard that Google hopes will transform the Web from a collection of relatively static sites to a foundation for full-blown applications that rival those on PCs.
The "video" tag in HTML already is available in various versions of Apple's Safari, Firefox, and Opera, which at least in theory makes handling video on the Web as easy as handling images. But the HTML 5 standard that includes video isn't finalized yet, so don't expect a coding revolution yet.
The video tag can be used to show video that today would show up in a conventional box, just as with Flash or Microsoft's competing Silverlight plug-in. But it also enables deeper integration with a Web site. For a good example, watch Paul Rouget's demonstration of HTML video in which images, text boxes, and videos are overlaid on another video, with a JavaScript program dynamically changing the appearance.
In a talk Wednesday at the Google I/O conference, Matthew Papakipos, a Google engineering director, said HTML 5 video will permit close integration with the Web site's programming, so for example various actions on the Web site can trigger different videos to start or stop.
The video tag tucked in Daily Motion's Web site could be a harbinger of significant changes on the Web.
(Credit: Screenshot by Stephen Shankland/CNET)HTML 5 video still faces many hurdles to adoption, and browser support being just the first. Next come resolution of browser compatibility problems, upgrades by browser users to support the feature, and real-world use of the technology on Web sites.
The challenge is illustrated by video entertainment site DailyMotion, which on Wednesday announced plans to make 300,000 videos available through the HTML 5 video technology by the third quarter of 2009. DailyMotion recommends the Firefox 3.5 beta version to watch videos, which indeed worked for me, but the newest Chrome developer version and the Safari 4 beta reverted to Flash.
DailyMotion touts its use of HTML 5's video tag to show videos encoded with Ogg Theora technology--but the feature doesn't work with the Safari 4 beta or the latest version of Chrome.
(Credit: Screenshot by Stephen Shankland/CNET)One issue is the technology used to encode and decode video. Firefox supports the Ogg Theora format for video (and the Ogg Vorbis format for the related HTML 5 audio tag), for example, and that's the format that DailyMotion is using.
More common in the real world, though, is the H.264 standard. Papakipos said Chrome will support H.264 video and AAC audio as well as Ogg Theora video and Ogg Vorbis audio format.
Stephen Shankland writes about a wide range of technology and products, but has a particular focus on browsers and digital photography. He joined CNET News in 1998 and since then also has covered Google, Yahoo, servers, supercomputing, Linux and open-source software, and science. E-mail Stephen, or follow him on Twitter at http://www.twitter.com/stshank. 



ihttp://acid3.acidtests.org/
Also, IE will most definitely be the last to support the key features of HTML5. Why does the world have to wait for Microsoft, when all the other browsers are in the process of rolling out support for HTML5?
If I were a developer writing JavaScript applications for a living, I would be pulling my hair out over browsers. What JavaScript I have written was rather frustrating. So, I feel your pain. It is like trying to write software for n different platforms wherein every operation has to be checked to see if it might even work or not on a given platform. Code can get seriously bloated and the logic gets burried under all of the conditional house-keeping logic.
But, is removing IE the fix? No. Why? Because there will be something new next year. Users will be forced into a constant state of upgrade, upgrade, upgrade. And, as a developer, you will still be forced to have a lot of complex conditional code to make sure things work right, most of which you cannot thoroughly test -- or at least you would be greatly challenged to test every code path. And, even if you get your code working right on Firefox today, that does not mean it will work in the next release: something might break. Browser upgrades do impose similar risks to OS upgrades. Sometimes, it is even worse: I can write code (excluding drivers, as those are special) for any OS and make fairly sure it will work on a subsequent release. Code in a browser can break and there's nothing I can do because I have no control over the exection environment.
The root of the problem is that JavaScript is the basis of web development. There are some nice aspects to the language, but lots of things I hate about it. Developers should have more choices for application development in a web environment.
For those interested in web development (particularly client-side stuff), one ought to be more concerned with things like the fact that one has extremely limited tools to use. The browser is an over-stretched document viewer. What is truly needed is a new client-side application framework, something quite different than today's browser. Perhaps a client side tool that is designed for applications first and foremost, rather than documents (like today's browsers).
b) Safari sucks, it's installed without prompting.. that is called 'spyware'.
c) IE is a better browser, it is safer, faster, more compatible. Firefox / Chrome are half-breeds. Sorry.
d) Adobe is a common enemy.. but I'll bet that google is just trying to lower their stock price (so google can buy Adobe)
What planet are you from? IE is the slowest, least secure .AND least standard compliant browser you can use. Run the acid3 test on IE and then on any of the other browsers. Microsoft should be embarrassed.
- by maeckg May 29, 2009 4:34 PM PDT
- Paul Rouget's demo ran smoothly in Opera 9.64, which is stable and finished already. Really cool than cool demo.
- Reply to this comment
-
(18 Comments)