Click on the image below to watch a 1 minute screencast of it in action – or you can try it yourself here (I’d recommend you use the latest Firefox nightly with JIT turned on – but the demo works in Firefox 3 and Webkit nighties).

Boris Zbarsky landed support for querySelector[All] just before Firefox 3.1 Alpha 1.   Recently John Resig and Mike Morgan took the slickspeed selectors test from the Mootools project and updated it with versions of most of the toolkits that support native querySelector. 

The results are an impressive ~3-7x speedup!

The raw times looks like thus:

You can try it yourself here (make sure to use a Firefox 3.1 alpha or nightly build after July 22). Since all major browsers will soon support this feature the entire web is about to get a pretty big performance boost.

More great stuff is on the way for Firefox 3.1…

This is not new news but I did want to provide my perspective on why this is important.

If you read the HTML1.0 specification from 1993 carefully you’ll notice it doesn’t specify the image format even though there are dozens of them. GIF is excellent for logos, line drawings, etc but is limited to 256 colors and is thus non-ideal for photos.  JPEG is lossy-compressed and thus great for photos but less suitable for vector art and drawings.   PNG came later to work around some issues in GIF and wasn’t fully and properly supported in Internet Explorer until version 7.  Before PNG was fully natively supported in all browsers there were many plug-ins to fill the gap.

A patent encumbered technology (GIF) critical to the web was replaced by a truly open and free format (PNG) first through plug-ins and then quickly after natively in browsers.  The HTML specifications did not specify a particular image format but a few became ubiquitous through common usage.

This is where I believe we are going with <video> and <audio> tags.  Right now hundreds of millions of users can view videos in their web browsers, but it requires one of several proprietary plug-ins which support proprietary formats to play.   This means if you build a website with flash/silverlight/WMV  video it will not work on millions of iPhones and other mobile browsers.  It may or may not work on Linux.  Getting it to work requires lawyers, money, and business agreements between multiple parties.

By shipping HTML5 <video> and <audio> with royalty free open source formats in Firefox we hope to make these formats ubiquitous through common usage.  Royalty free open source formats will allow all web-browser makers to enable native video and audio playback on all platforms, devices, and environments, without restrictions.  They will allow all open source products to embed native video and audio playback without fear.   They will allow web authors to use audio and video freely in their websites without worrying about whether a particular platform has a particular version of a particular plug-in installed.  As an end-user we soon won’t have to worry about whether we can watch video content from a particular website on our new phone, tablet, or PC because all systems can support open video standards.  Perhaps I’ll be able to watch the 2010 Olympics on my mobile phone.

True ubiquitous access to content.   This is the world we want.

There’s not much content encoded in Theora/Vorbis at this time – what’s the point?

Ten years ago there wasn’t any content in H.264 but it is fairly common now.  Until Flash video became common there wasn’t a ton of video content encoded in VP6.   New content is created all the time and transcoding to Theora/Vorbis is quite simple.   Shortly after Firefox 3.1 ships there will be almost 200M desktops capable of playing this kind of video.  Content should follow quickly.

I can already watch video using Flash, Quicktime, Sliverlight, etc so what’s the point?

Having native video/audio support as part of HTML5 along with open source and royalty free formats means that every browser vendor, device, etc can support this format.  If adopted widely it means that web authors will soon be able to use one format to target all devices.  As a native web technology video can now be intermixed with all other advancements in the web as seen here.

Doesn’t Theora kill battery life and/or eat CPU time?

Many systems today ship with some form of hardware acceleration for H.264, MPEG-2, and other formats which reduces their CPU usage and thus battery usage.   With adoption of the format we expect Theora to benefit from similar hardware acceleration in the near future.  In the meantime HD video at 5-6MBp playes smooth on modern system without any hardware assistance.

Doesn’t the video quality of Theora suck?

It is very watchable and getting better all the time with work such as this.

Are there any legal issues?

We’ve done a careful legal analysis of all known issues and to the best of our knowledge Theora and Vorbis do not pose any patent risks. They’ve been around for a while with no issues; however, there is always the risk of what folks call submarine patents but this risk occurs for every software developer writing any kind of software.  There’s also always a risk someone asserts a claim, which doesn’t necessarily mean that the claim has any merit.  We believe there are no issues, but if push comes to shove we can: i) evaluate any claim and determine if its meritorious; ii) use the power of the web to gather relevant prior art to demonstrate invalidity; and iii) remove or disable the functionality quickly if necessary as a last resort.

What about HD?

Theora can play and encode HD content.  Based on current implementations the video quality is not as good as H.264 but much can be improved.  In addition we’ve been talking to the fine folks behind Dirac and I’ve seen some very impressive looking 720P videos encoded in Dirac.   The good news is once we get the basic video/audio infrastructure into Firefox adding new codecs/formats will be relatively straightforward.  This is just the starting point to get baseline video capabilities ubiquitous.

Why didn’t you just license H.264, VC-1, MPEG-2, or <insert favorite codec here>?

We looked very carefully at this option and we could have very well done this for all “Official” Firefox binary releases at significant monetary cost to us.  But this had several issues:

• It would require the inclusion of close-sourced code into Firefox.
• Any derivatives of Firefox or Mozilla code would *not* be able to ship it.
• No other open source project would be able to use it.

This would solve the problem solely for Firefox users. We are more interested in solving the problem for the entire web.

Why not just use native Directshow/Quicktime/GStreamer on each platform?

We are working on this as well as you can see here, here, and here.  However, this approach has two major limitations: a) codec support varies dramatically from platform to platform and b) this does nothing for phones or other systems.  We wanted a baseline format that all web authors can count on in all environments.

This is awesome, how do I help?

Download a Firefox nightly build here and test it out here or on Wikimedia Commons.  Produce native content in Theora/Vorbis.   Help transcode other formats to Theora.  Tell your friends.

It really has been a singular honor to have been part of Mozilla and I’m hugely proud of what we’ve been able to accomplish together. We’ve shipped Firefox 1.5, 2, and the amazing Firefox 3 together, taken the active users from tens of millions to >185 million in almost 50 languages, achieved 50% market share in some countries, built a thriving Add-ons ecosystem, moved into mobile, scaled our operations across the globe, and most importantly of all continued to build a thriving, passionate, talented community that is a blast to be part of.  This is the first time I’ve decided to leave something I really truly love – I will dearly miss getting a chance to work with all of you every day. Everyone that I’ve met from the community has, and will continue to be, a huge inspiration to me.

I *know* that Mozilla will continue to kick butt without me – impossible to do otherwise with the strength, talent, and passion of the people here.

Rock on,

Schrep

At the beginning of 2007 we had approximately 25k daily users of the early FF3 builds, that number grew to 50k as we approached Alpha 8 and last week there we over 2,000,000 daily users of Firefox 3.  The daily public builds, many many major milestones, and thousands to millions of testers are all part of our process to ensure that Firefox 3 is the best browser you’ve ever used.  We are still collecting feedback on RC2 and putting the final touches on the assoicated web sites around the Firefox 3 – but the final version is coming very soon.