As a good citizen in the Mozilla developer community, you need to watch the tree, and star any random oranges with bug numbers, and put a comment inside the relevant bugs with a link to the log of the orange in order to help debugging the problem. That's too much work, and worse, it's repetitive and boring. Last weekend, I got sick of it, and decided to hack Tinderboxpushlog to make this a bit easier.

I just landed a set of patches on mozilla-central which makes the initialization of the editor for text fields (input type="text” and input type="password” in HTML terms) lazy. What we used to do was to initialize the editor component for text fields as soon as we created frames for those elements. This was not ideal, because users don't usually use all of those fields on web pages (think about the “search” text fields you see on every website nowadays, for example.

Atul Varma has built an user name autocomplete tool for Bugzilla. This reminded me that it's been a long time since I wanted to add this functionality to the Bugzilla Tweaks jetpack. Last week I added this feature, but I didn't get the time to blog about it! Here is how it looks on a a sample bug: It is also smart enough to handle multiple users for fields which accept it.

If you use Firefox nightly builds, and you had the Jetpack Prototype installed, you might have noticed that about two weeks ago, your jetpacks had started to get disabled a short while after you had opened your browser. This issue was really frustrating, since some of us run jetpacks which are very important in our daily work. I filed bug 554169 about this issue. Paul O'Shannessy fixed this, and earlier this week, the Jetpack team released a new version of the Jetpack Prototype which fixes this issue.

I really needed a context-sensitive C++ autocomplete feature for Vim, which would allow me to do crazy things like autocompleting class member names. As it turns out, there is a way to do that, and it works pretty well. I decided to write up how I set things up myself, in hopes that this will help others as well. Here is what you need in order to set things up:

The ability of editing HTML content on the web is nothing new, we've all used it to write emails in Web-based email clients, post content on our blogs, adding content to web sites, etc. Web sites usually do this using the execCommand API, with either iframes put into designMode, or contentEditable elements, and occasionally utilize things such as the DOM Range API and Selection API. Things sound great, but in practice, they're not.