howto

You are currently browsing the archive for the howto category.

A quick note if you’re going to be using OGG open web video hosted on web servers.  There’s an important configuration change that you should make so that Firefox recognizes it as video.  In my Apache configuration I’ve added this directive:

AddType application/ogg .ogg
AddType application/ogg .ogx
AddType video/ogg .ogv
AddType audio/ogg .oga

Most web servers are likely to return the mime type as “text/plain” which Mozilla will not show as video.  If you don’t set it, and it’s served up as text/plain then Firefox is likely to show either an error or endless buffering.  (Although I suspect that the endless buffering is actually a bug in our internal player and will likely be fixed.)

Update 1: This should have been video/ogg for .ogv, application/ogg for .ogg, and audio/ogg for .oga files.

Update 2: You should look at this post from Silvia for the correct information. Thanks, Frank.

Some of you might have noticed that I was able to use a fallback in my previous posts that include a native video tag. I was going to do a post on how that works. It’s pretty simple.

But Chris Double beat me to the punch and has an excellent little tutorial about how he’s using the video tag with elegant fallbacks. (In his post you can use something other than the Java-based fallback. In my case I linked back to vimeo.)

Enjoy!

Asa points out some incorrect information in an article on Wired about following different branches of development on Chrome.  We’ve been doing this at Mozilla for years and years but I thought it might be worth documenting how to do this for people who want to follow our final releases, beta builds, beta nightlies and trunk nightlies.

Firefox final releases.

These are the builds that show up on the main page on mozilla.com.  The current build is Firefox 3.0.5 and users who previously have downloaded and installed Firefox 3 are automatically updated to builds as we release them.  They are generally done on a 6 week schedule, or as security or bug fixes require.

Firefox 3.1 does not have a final release yet and as such it’s not on this page yet.

Firefox beta builds.

There is a link on mozilla.com to download released betas.  If you’ve downloaded and installed one of these betas you will also be offered betas as we release them.  Once we move from beta to release candidate, you will be offered upgrades to the release candidates and eventually to Firefox 3.1 final when it’s released.

Firefox beta nightly builds.

As of the writing of this entry, Firefox 3.1 development has branched and our beta, release candidate and 3.1 final work is being done on a separate branch.  We generate builds every day for people to test beta functionality.  You can find the built nightlies on our download server in the latest-1.9.1 directory.  (In addition, have a look at our mozilla QA project (QMO) for information about how to get involved!)  If you’re following this set of builds you will get the opportunity to update one or more times a day with new builds.  As of Beta 2, these builds are pretty stable and these are what I’m currently running for all my day to day work.  You can tell these are the beta builds because they are named “Shiretoko.”

Firefox trunk nightly builds.

This is the rawest of the raw (although still not too bad!)  This will eventually become Firefox 3.2 or Firefox 4 or whatever we end up calling it.  Fixes that are set to land in the Firefox 3.1 branch land here first, so it’s a place to test out fixes before they make it to the beta channel.  You can find these builds in our latest-trunk directory.  You will likely see more instability and bugs here.  Updates are done daily, or sometimes more than once a day.  If you’re running these you definitely want to be involved in our QMO effort.  You can tell these are trunk builds since they are named “Minefield.”

Hope this helps – enjoy!