Not available yet? What century do you come from?
WebM has been supported in Firefox since 4, Chrome since 6, and Opera
since 10.6.
It's also apparently supported by Opera Mobile since <video> was
introduced and the Android browser since Gingerbread.
And where do you get off talking about h264 as modern format from this
century. h264's development started in the 20th century, it's been almost
10 years since the format was standardized. If you want to talk about
modern and this-century then you should be pointing to WebM which was
standardized recently in this century.
I do have one thing to say. I don't think we should drop plans to support
WebM. At the very least, if we do decide to add additional support for
h264 we should make sure to use <video> tags which include both a WebM and
h264 source.
--
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [
http://daniel.friesen.name]
On Mon, 19 Mar 2012 20:12:45 -0700, Mono
monomium@gmail.com wrote:
> Please. Although WebM is a promising format, it's not available yet. The
> Java fallback is a solution even worse than just using Fash, so if we
> want
> to get with this century, I believe we have to hold our noses and adopt a
> modern format.
>
> On Monday, March 19, 2012, Brion Vibber
brion@pobox.com wrote:
>> As some may know, we've restricted videos on Wikimedia sites to the
>> freely-licensed Ogg Theora codec for some years, with some intention to
>> support other non-patent-encumbered formats like WebM.
>>
>> One of our partners in pushing for free formats was Mozilla; Fire fox's
>> HTML5 video supports only Theora and WebM.
>>
>> The prime competing format, H.264, has potential patent issues - like
> other
>> MPEG standards there's a patent pool and certain licensing rules. It's
> also
>> nearly got an exclusive choke hold on mobile - so much so that Mozilla
>> is
>> considering ways to adopt H.264 support to avoid being left behind:
>>
>>
>
http://blog.lizardwrangler.com/2012/03/18/video-user-experience-and-our-miss...
>>
>> Is it time for us to think about H.264 encoding on our own videos?
>>
>> Right now users of millions of mobile phones and tablets have no access
>> to
>> our audio and video content, and our old desktop fallback of using a
>> Java
>> applet is unavailable.
>>
>> In theory we can produce a configuration with TimedMediaHandler to
>> produce
>> both H.264 and Theora/WebM transcodes, bringing Commons media to life
>> for
>> mobile users and Apple and Microsoft browser users.
>>
>> What do we think about this? What are the pros and cons?
>>
>> -- brion