Thanks to new, easy-to-use standards, the Web just got a lot more animated.
There are some really compelling demonstrations out there that showcase the use of video in conjunction with WebGL and other modern web standards. For example, the spinnjng cube at webkit.org and video shader demo from the 3 Dreams of Black interactive film give you a taste of what’s possible when Web pages go 3d.
Three-dimensional effects don’t yet work in every browser, however. Some have been hard-coded to work only in Chrome or Safari, though Firefox should support them soon.
Confused? Help is on the way.
A new website helps web developers decipher the often confusing world of HTML5 and CSS 3. Which elements are ready to use? Which are still not widely supported? And where can you find polyfills and fallbacks for older browsers? HTML5 Please has your answers.
For many developers, the best thjng about HTML5 is that it will drastically simplify the now byzantine process of adding video and audio to a Web page. Here’s a report just on exactly where it’s safe to use this new technique:
For a very thorough rundown of exactly where and how well HTML5 video works on the web right now, check out the excellent report on the state of HTML5 video from Long Tail Video. Put together by the makers of JW Player, an HTML5 video player toolkit, the state of HTML5 video report is mercifully free of any evangelism for any particular technology. Instead it offers a level-headed look at reality, answering the basic questions — where can you use HTML5 video? How well will it work for users? And when will you need Flash fallbacks?
Firefox 10 now has a suite of sophisticated developer tools baked in–though my early tests suggest that its popular add-on Firebug remains the best debugger in the business.
Mozilla has released Firefox 10, which features new and improved tools for web developers as well as more support for emerging web standards.
One problem that Mozilla hasn’t solved is less technical than philosophical: whether to add DRM to an open video standard so Netflix et al. will adopt it.
“The problem is that some big content providers insist on onerous DRM that necessarily violates some of our open web principles (such as web content being equally usable on any platform, based on royalty-free standards, and those standards being implementable in free software),” O’Callahan wrote. “We will probably get into a situation where web video distributors will be desperate for an in-browser strong DRM solution ASAP, and most browser vendors (who don’t care all that much about those principles) will step up to give them whatever they want, leaving Mozilla in another difficult position. I wish I could see a reasonable solution, but right now I can’t. It seems even harder than the codec problem.”