Mozilla Firebird — Now with DOM Inspector!

The DOM Inspector was checked in to the Mozilla Firebird trunk today and it should appear in tomorrow’s nightly builds. For those not aware, the DOM Inspector is the ultra-useful browser extension for — among other things — analyzing CSS within a webpage. For instance, you can select an element on a page and the DOM Inspector can tell you how the document’s CSS rules cascaded to produce that element’s styling.

I’m really stoked about this check-in since the missing DOM Inspector was one of the few things holding me back from Mozilla Firebird. Now if I can just get URLs from Thunderbird to open in a new Firebird tab, I’ll be all set :). And, some say that there’s a solution to the open-new-tabs issue as well.

I don't doubt that switching to Firebird/Thunderbird is a Good Idea(tm), but I'm still unsure when the development team will officially make the switch. Reading over the roadmap, they say that “[it’s] clear now that we will not be able to switch to Mozilla Firebird by the Mozilla 1.5 final milestone” — but they don't elaborate on when they expect that switch might be :-/.

Update 11-13: I’ve discovered that Firebird still doesn’t have inline autocomplete in the location bar (URL bar). Bummer.

5 thoughts on “Mozilla Firebird — Now with DOM Inspector!

  1. The lack of inline autocomplete drives me nuts too. I see no point for the pull down method ever. If I wanted something pull down I would have clicked a button or something.

  2. I, on the other hand, prefer the current behavior and was always annoyed by the inline autocomplete; I prefer that when I type an address and press enter it actually goes to the address I typed rather than what it thinks I meant. And when I do want it to complete my typing, it shows me a list of matching sites and I can easily press tab-enter if the first item matches. Personal preference, I guess.

  3. Inline autocomplete interferes with the use of shortcuts. Perhaps if modifierKey-return/enter were available to enter as typed rather than as completed (and a preference for vice versa) we’d all be happy.

  4. Is there anyway to stop the autocomplete from happening? I know you can lock the history.dat, but that also stops visted links from marking. I just want to prevent autocomplete on the location bar.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.