How Firefox Loads Plugins

While debugging getting plugins working again with the CCK Wizard (it broke when Firefox removed platform specific directories in extensions), I learned a lot about how plugins load within Firefox. In particular, I learned a lot how to stop Firefox from loading plugins from different locations. So I thought I would share. Note that this post is primarily about loading plugins on Windows.

Customizing the Firefox Installer on Windows (2012)

This is an update of a previous post. It has some new questions answered as well.

One of the questions I get asked a lot is how to customize the Firefox installer on Windows and how to bundle add-ons with it. This Q&A should give folks answers to the common questions they have. If you have more questions, please post in the comments.

Making Firefox 10 More Like Firefox 3.6

Update: A preference was introduced in Firefox 12 for allowing tabs on bottom. I've update the add-on to account for this.

With the release of the Firefox 10 ESR and the upcoming end of life of Firefox 3.6, I am getting more and more requests to add functionality to the CCK to make Firefox 10 look more like Firefox 3.6. Rather than add those features to the CCK, I'm providing a separate add-on to satisfy that need.

Resolving Intranet URLs

On problem with Firefox that enterprises commonly report is that there is no easy way to tell Firefox that http://name is a URL on your intranet. Firefox will go through the normal process of attempting to add www and com to the name and it will fail. I think I've found a solution.

Happy Belated New Year!

One of things that has kind of become a tradition for me is the New Year's message at my church.

The message this year was focused was on creating new habits. I called it "Helpful Habits for a Happy New Year."

The five areas I picked were:

  • Physical Habits
  • Intellectual Habits
  • Financial Habits
  • Emotional Habits
  • Spiritual Habits

I would encourage you in this New Year, pick a couple of those areas and come up with new habits that you are going to start. And habits you are going to stop.Then write it down! Keep yourself accountable. And make this a great new year.

If you'd like to give it a listen, it's here.

The CCK and Firefox 8

URGENT UPDATE: Using distribution.ini to set extensions.disableScopes does not work in Firefox 8. I've opened a bug for this. The only workaround is to create a JS file in the defaults/preferences directory (you will have to create this directory) where Firefox is installed and set the value there:

pref("extensions.autoDisableScopes", 0);

Also, note that the correct value to disable this feature is 0 (zero).


I've received my first email about the fact that with Firefox 8, users are now asked if they want to disable your CCK, depending on how you chose to install it (probably in one of those places that Mozilla now considers "forbidden")

If you have NOT deployed Firefox 8, in your organization yet, you need to read this article about disabling the various dialogs that appear.

The problem is that you need to set these preferences in Firefox 7 via something like the CCK so that the dialogs won't appear. If you're already moved to Firefox 8, it's too late.

In the future, it is now recommended that you ship your CCK using the distribution mechanism which I documented last year.

Honestly, there's no really good solution to this for enterprise, but the right place to participate in the discussion is the Enterprise Working Group Mailing List. (Although there isn't much discussion going on there anymore.)

Solving the Bugzilla Backlog

I've been doing a lot of complaining lately in directly violation of my first post of the year.

Going forward, I'm going to try harder to offer solutions instead of just doing a lot of complaining.

So, lately with Tyler Downer's post, there's been a lot of talk about Bugzilla and triage and other things. Yesterday, I was debugging a problem and discovered a bug that had been open for 5+ years with no fix (even though the component it was in had been rewritten in the mean time). (And before you ask, yes I posted a patch.)

The fact is that Bugzilla is a mess, not just with unconfirmed bugs, but with bugs that are no longer relevant, bugs that have already been fixed and more.

So here's my thought:

Stop all non critical activity on the Mozilla project for one week. All development, all test, etc. Have everyone in the community (and I mean everyone) attack Bugzilla and get it as cleaned up as possible. Have awards for the people that resolve the most bugs.


Improving Stakeholder Communication in Firefox

As I've been watching this rapid release thing continue to unfold, I've been thinking about what it is that truly went wrong in the messaging. The fact that at this point, Mozilla executives are having to continue to try to sell this to people means that something went wrong in how they executed the change. As I thought about it more and more, I realized what a big part of the problem was - stakeholders.