2 ms·
Right now, two codecs cover all the browsers that matter. Internet Explorer supports WebM, but doesn't ship with the codec; Google provides the WebM codec for
by JoshTriplett 15y ago
Right now, two codecs cover all the browsers that matter. Internet Explorer supports WebM, but doesn't ship with the codec; Google provides the WebM codec for Internet Explorer (https://tools.google.com/dlpage/webmmf https://tools.google.com/dlpage/webmmf). That just leaves Safari and iOS that still only support H.264.
Personally, as JavaScript engines get faster, I hope for solutions like this in the future: http://badassjs.com/post/13551173773/route9-js-a-vp8-webm-decoder-in-javascript http://badassjs.com/post/13551173773/route9-js-a-vp8-webm-de...
Meanwhile, if Adobe would ever get around to adding WebM in Flash as previously promised, that would work as a fallback for Safari, as well as IE users without a WebM codec, leaving just iOS.
- ZeroGravitas 15y agoSafari (on Macs) has had a codec plugin support mechanism for codecs for a long time via Quicktime, and I believe WebM is already supported in Perian, the popular ffmpeg/libav wrapper for OS X.
- JoshTriplett 15y agoInteresting, but that doesn't seem like something straightforward to convince a random site visitor to install. Google's WebM plugin for IE seems like a hard enough sell even with Google's name attached to it.
- ZeroGravitas 15y agoGoogle did promise a plugin for Mac OS X too, and "soon" when they announced the IE one about a year ago (http://blog.chromium.org/2011/01/more-about-chrome-html-video-codec.html http://blog.chromium.org/2011/01/more-about-chrome-html-vide...) though there's been no sign of it since. I doubt it's beyond their ability, particularly as someone's demonstrated that it can be made to work. I'm guessing though that they'd be generally happier if people on Mac OS X just used Chrome. There's less likely to be Safari users who are forced to use the browser due to IT department dictates or whatever other odd reason people use to justify IE.