Notes on Firefox development

Today marks the start of my third week at Mozilla. I’d like to mark this occasion with some things that I have learned that are pertinent to developing for Firefox.

1. review?

   When I submitted my first patch to Mozilla, I added a reviewer by appending r=reviewer to my patch. While this may say what you mean, it doesn’t do what you mean.

   To properly request a review, set review to ? in Bugzilla when you are adding an attachment. This will properly email the reviewer so they can become aware of the request.

2. make -s -C objdir

   Running a clean build of Firefox can take about 25-30 minutes, while an incremental build can still take about 2 minutes. This is clearly not conducive to an iterative-style of coding.

   To make builds faster, you only need to rebuild the parts that have changed. To do this, simply run make -s -C objdir, where objdir is the parent directory within the object directory of the code that you have changed. It may be necessary to also re-link if native code has changed.

3. -moz-appearance: none

   This was the first XUL gotcha that I ran into. I bumped in to this as I was working on bug 598169 and trying to make a XUL:textbox styleable.

   Many XUL elements use OS-dependent styling, and if you want to apply styles to them then you will have to turn off the default styling. -moz-apperance: none does just that.

4. hg qpush –move patch

   Many of the developers at Mozilla use the mq extension for Mercurial. mq is a tool that allows you to keep all of your changesets in separate queues. This makes it easier to work on different patches in parallel.

   Most work can be done with three of the mq commands: hg qnew, hg qpush, and hg qpop.

   A normal hg qpush patch will push the current patch as well as all preceding patches on the tip, whereas hg qpush --move patch allows a user to push just the single patch on the tip.

5. pymake

   If you’re working on Windows, Firefox can take a while to build when using the standard make -f client.mk. Fortunately, there exists a tool that makes your builds run a lot faster by taking advantage of the multiple cores on your system.

   Running python -O "..\build\pymake\make.py" -s -j12 will build Firefox with 12 concurrent compilations. I chose 12 because it is 1.5x the number of threads on my system. :dolske ran some benchmarks to find the optimal -j setting and advised me on the 1.5x multiplier.

   You can learn more about pymake on the Mozilla development website.

View source code for YouTube Playlist Downloader online

I’ve just uploaded the source code for the YouTube Playlist Downloader online to Google Code. You can view the source by browsing the trunk on the YTPD Google Code site.

The download link will stay the same since ClickOnce isn’t supported on Google Code. I may find myself adding in the setup executable to the download area within the Google Code project, but that executable will simply point at my metrolansing.com domain due to the aforementioned issue.

I’m using Mercurial for the version control system, and it is my first time working with a distributed version control system (DVCS). I’m looking forward to being able to work in branches and move complete features in to the trunk. From my first steps that I have taken, these DVCS systems seem to be the inverse of systems like Subversion. In Subversion, most work is done in the trunk, and then releases are either moved to a branch or tagged, whereas in Mercurial work is done in branches and then merged in to the trunk when considered complete.

Feel free to peruse the code and lend me any suggestions you may have. I am actively looking for contributors, so if you would like to get involved in some WPF and C# then you may have just found the project you were looking for.