Filing Bugs in Components

I’m always filing bugs, and I usually know the Bugzilla component they’re supposed to go in. So I made a shortcut to get around the hoops of picking a component on the Bugzilla form. It’ll autocomplete on product and component name for faster filing:


I also often search for bugs by summary in a component, so I made a shortcut for that too. You can search for open, closed, or both:

I’m interested in the common fields other people use when searching for bugs, so if you have any insight leave a comment.



Seeking New Owner for Nightly Tester Tools

Nightly Tester Tools is an addon for Firefox nightly and beta testers. I’m the current maintainer of the addon, having been passed down the torch by Dave Townsend. It’s at the point where I no longer have time to give Nightly Tester Tools the attention it deserves.

Nightly Tester Tools has been around for a long time. It’s provided tools like build id copying, screenshots, and test crashing. The code is currently on Github, and there’s a Bugzilla component Other Applications/Nightly Tester Tools Where people file bugs.

Maintenance mainly involves bumping the version compatiblity on AMO every time there’s a new Firefox release and checking out new bugs or feature requests that come in.

This is a great opportunity for a nightly tester to build onto a tool that helps out thousands (NTT has about 100,000 users) of testers, and learn some extension development at the same time.

Please get in touch if you’re interested. I’m harth on #ateam on and always available to answer questions about it and guide anyone along about the process.

Rainbow Update

A new version of Rainbow is out. This new version contains a bunch of tiny fixes that make it 10x more useful I think:

Extract color schemes from images

Extract the color scheme from any image on the page by right-clicking the image and selecting “Extract Color Scheme”:

Preview element colors

There’s now a “Preview Element Color” context menu item that will let you quickly inspect the background/text colors of any element in Rainbow’s color picker:

View last color

View whatever color was last copied/saved from the inspector with the “View Last Color” shortcut in Rainbow’s main menu:

This version also adds a French localization courtesy of Alain Besancon and some much-needed bug fixes.

Anyways, the real news is that 1.4 is the last version I’ll release on this code base barring any new locales or bugs. Soon I’ll be starting a complete re-write that might take awhile. The current code is written by a total JavaScript and programming n00b (me, four years ago) and uses XUL (thus can’t use Jquery or any nice new HTML features).

I’ll be converting it to HTML, modularizing it (starting with, and making it a Addon-SDK-based addon and creating a Chrome extension if all goes well.


I just published replace, a find-and-replace command line utility that others might find useful. I’m always wanting to replace strings spread throughout my code, and never found an easy way to do it. `find` + `sed` can do it, but the syntax is hard to remember and you don’t get easy-to-read feedback on what replacements are made. It’d be cooler if there were a tool devoted to this.

Replace takes a regular expression string (in JavaScript syntax), a replacement string, and files to search (or directories to search recursively when `-r` is specified). It will print out the lines that have been replaced:

screenshot of replace

There are quite a few other options and output choices, check out the GitHub for more information. It requires installing node.js and its package manager npm if you don’t already have them. Then you can install with:

npm install replace -g

Side note: It’s true that JavaScript is still quite a bit slower than bash/C, so it’s good to question why you’d write something like this in Javascript. I blame how nice it is to write programs in node, how nice it is to handle dependencies and distribute programs with npm, and all the really well-done node libraries out there (like colors for coloring console output). This is something I wouldn’t have taken my free time to write in any other environment.

Nightly Tester Tools Update

Nightly Tester Tools 3.0 has been released, containing some new features. Among the added features are Crashme functionality, copying about:support to pastebin, and viewing the pushlog of changes since the last nightly.

Since the update about the future of Nightly Tester Tools, there’s been some discussion around the addon compatibility feature. We decided to take out addon compatibility fixing for individual addons, but left in a checkbox that overrides compatibility checking for all addons. It works in the same way Addon Compatibility Reporter does, but everyone’s encouraged to install ACR to help report compatibility issues to addon authors.

Screenshot of Nightly Tester Tools Firefox menu

Mobile version

Aakash has been working on a mobile version of NTT, with a few of of the same features of the desktop version and a few mobile-specific ones. Nightly Tester Tools 3.0 for mobile has also been released.

Screenshot of mobile Nightly Tester Tools

You can request a feature by filing an NTT bug. Check out the code on Github (mobile code here).