High-ranking Mozilla staff, believing they've lost a fight to keep patent-encumbered technology off the Web, have concluded it's time to change course and support H.264 video technology.

The H.264, a "codec" to encode and decode video for more efficient storage and streaming, is widely used in everything from video cameras to mobile-phone processors. However, it's encumbered by patent royalty payments that go against Mozilla's goal of fostering an open Web.

The patent issue led Mozilla to strongly endorse Google's alternative VP8 codec that's part of its royalty-free WebM project. But WebM just isn't catching on, and Google hasn't fulfilled a promise to remove H.264 support from Chrome to try to promote WebM, so Mozilla Chief Technology Officer Brendan Eich and others responsible for Firefox have reluctantly endorsed a change of plans.

"The pressure to promote WebM was needed from a bigger player than Mozilla, and it was needed a year ago," Eich said in a long mailing-list discussion. "It might not have worked then, even with Google on-side. Now, with just Mozilla going it alone, all we do is kill our mobile initiatives in order to appear pure...That does not serve our mission or users."

Those Mozilla representatives who came around to H.264 endured a lot of criticism for insufficient purity and principle. But clearly they went through a lot of soul-searching beforehand.

First-class Web video
Mozilla and Google had hoped to make video a first-class citizen on the Web, as ordinary and easy to use as JPEG images are today. But H.264's dominance means that patent-licensing payments are effectively being built into the Web. Through an organization called MPEG LA, patent holders collect royalty payments from organizations that ship H.264 products or that transmit H.264-encoded video for a fee.

H.264 is the leader, far and away, when it comes to HTML5 video, according to a December 2011 study of 50 million videos by MeFeedia.
MeFeedia

It's not clear yet what exactly will happen with Firefox and H.264, but the thread began with discussing whether mobile Firefox should be able to tap into built-in H.264 support built into the operating system. Even this mechanism, indirect and limited to mobile devices, triggered disgust.

"Keeping the yucky stuff in third-party code doesn't really help keep it off the Web," said Henri Sivonen, an HTML5 expert and freelance programmer who consults for Mozilla. And Joe Drew, a Mozilla graphics programmer, added, "I am very concerned that, by supporting system codecs, we're simply capitulating on Free codecs"--free in the sense of free from patent-licensing constraints.

But for the most part, Mozilla authorities seemed inclined to add H.264 support. Endorsing the approach were Eich and Robert O'Callahan, who oversee the codec support in Firefox, and Andreas Gal, Mozilla's director of research and the programmer who launched the H.264 discussion.

Compatibility conundrum
The issue matters because streaming video on the Web is in the midst of a slow transition from using plug-ins such as Adobe Systems' Flash Player to the HTML5 standard that builds video support directly into Web pages. But the transition is easier said than done: HTML5 doesn't specify a codec because standards groups couldn't agree on a single one, which means Web publishers contemplating native Web video must reckon with browser compatibility problems.

On personal computers, compatibility isn't a severe issue, because Flash Player is ubiquitous on PCs and supports H.264. But for Mozilla, the issue came to a head because of how different things are in the mobile market.

Apple--the single strongest mobile player by virtue of its iPhone and iPad products--is a strong H.264 backer, and it barred Flash Player from Safari on iOS. VP8 and WebM support, meanwhile, still hasn't arrived on Android. That means H.264 is effectively the only way to go for mobile video.

Building H.264 support directly into Firefox would be fraught with problems given the impossibility of reconciling the open-source nature of the software with the royalty-payment requirements of the codec. What Mozilla's Gal proposed is an indirect approach that lets Firefox use the H.264 codec if it's built into the operating system.

With Android, the only mobile operating system of consequence where Firefox can even try to gain a foothold, H.264 support is built in. With B2G, H.264 support could be added to the operating system layer.

W3C

The debate began with mobile support, where Gal and others see H.264 as necessary, but it expanded to personal computers as well. That's because Windows XP and Vista--still widely used--don't have H.264 support built in. Consequently, some raised the possibility of Mozilla shipping H.264 support itself--perhaps as an extra module.

"If we want to support non-free formats via system codecs, we should make that our official plan for Firefox on all platforms," Drew said.

And the discussion didn't end at H.264. MP3 and AAC, two widely used audio codecs that also have patent constraints, also would fit in under the new Mozilla approach. "Anything the system has decoders for we should pass through and allow to work, including MP3 and AAC," Gal said.

Left in the lurch by allies?
In January 2011, Google pledged to drop H.264 support from Chrome, saying at the time in a blog post, "Though H.264 plays an important role in video, as our goal is to enable open innovation, support for the codec will be removed and our resources directed towards completely open codec technologies."

But today, Chrome still supports H.264.

Asked why, a Google representative said last month, "We have not backed off our plan to remove H.264 from the Chrome video tag, although we've not done so yet as we work with content providers to ensure a smooth transition."

The issue is somewhat academic, though: Chrome has Flash Player built in, so dropping H.264 support wouldn't be as likely to leave users in the lurch.

It's clear, though, that some at Mozilla feel they got a raw deal from Google.

"Google may not have intended to punk us into hurting ourselves (I don't think they did) but they certainly have wisely avoided hurting Chrome's market share by turning off H.264 decoding from [HTML5] video," Eich said. "They clearly are helping themselves by not turning off H.264 in Chrome, and they're not turning it off in [the] Android stock browser either."

"We don't have an update on when VP8 will be supported in Flash Player. We continue to work closely with Google on Flash Player and its support for popular video formats," said Danny Winokur, general manager of Interactive Development at Adobe, in a statement today. In any event, so far at least it's certainly not "in front of a billion people" as Adobe Chief Technology Officer Kevin Lynch had promised.

Even if Google committed today to dropping H.264 from Chrome desktop, the world has changed enough in the last year that I don't think even Chrome desktop's position can have much influence one way or another today.

The momentum was there a year ago. Maybe it was even still there 8 months ago. I don't think it's there today and Chrome alone probably can't restore that momentum. The rise of mobile and of iPad and the changing landscape for Adobe including streaming server support for H.264 for [HTML's] video> element (with no VP8 anywhere in sight) and the massive growth of Windows 7 compared to a year ago, where H.264 comes with the system and IE--too much has changed for the worse. Turning off H.264 in Chrome doesn't feel to me like it could change the course enough.

It seems there's plenty of dark mood to go around Mozilla's offices. "We've held the line, and watched, and waited, and personally I am extremely disappointed by the results," O'Callahan said.

Updated 9:38 a.m. PT and 12:45 p.m. PTto add comment from Adobe about VP8 support in Flash Player and to clarify Mozilla's position that Google's choices led to its choice.Updated 1:28 p.m. PT March 17to correct the name spelling and title of Asa Dotzler.

About the author

Stephen Shankland has been a reporter at CNET since 1998 and covers browsers, Web development, digital photography and new technology. In the past he has been CNET's beat reporter for Google, Yahoo, Linux, open-source software, servers and supercomputers. He has a soft spot in his heart for standards groups and I/O interfaces.
See full bio