One of the reasons that I enjoy my work customizing Firefox and building add-ons so much is that just about every request I get is a puzzle. They usually start with a question like “Is it possible for Firefox to…” or “Can you make Firefox…” When one of these questions is asked, I start going down the
rabbitfox hole and usually end up with some way to do what the client has asked. A lot of the same questions are asked so often that most of the time the answer involves giving them something I’ve already done or piecing together things I’ve already built. Occasionally, though, I get asked to do something that I’ve never done before. And that’s a lot of fun.
I found this post I wrote a year ago that I never published. With the renaming of Personas, it seems more relevant than ever. It’s time for Background Themes to get some love.
Personas Interactive (PI) from Brand Thunder integrates tightly with the Personas support in Firefox. Because the overhaul of the Add-ons Manager in Firefox 4 caused some major changes to the Personas code in Firefox (LightweightThemeManager.jsm), I had to revisit how PI integrates with Firefox. As I was working through those changes, I realized that many of the changes I’m making should not be a part of an add-on – they should be core functionality in Firefox 4. So what I’d like to do with this post is talk about three areas where Personas support in Firefox could be greatly improved. Those areas are Website Integration, Core Functionality and Extensibility.
In my earlier post on Integrating Add-ons into Firefox, I indicated the for some of the install methods, you have to set the preference extensions.autoDisableScopes to 0. In the comments, Blair McBride recommended against setting this preference to 0, because it would enable any third-party add-on install. Based on the feedback I’ve seen from enterprises since the release of Firefox 8, they simply want things to work the way they did before Firefox 8. to do that, you set the preference to 0. But Blair’s statement made me realize that a much better explanation of add-on scopes and the two related preferences was in order.
I’ve released version 1.3.4 of the CCK Wizard. It’s available here.
It has the following changes:
- Delete the previous CCK’s bookmarks upon upgrade.
- Install plugins in the correct directory
- Allow two CCKs to coexist
- Much better method for overriding about:config
- No longer use JAR files
- Bump internal versions to 10.*
A problem was discovered after I released this where if your Company Identifier contains a dash (-), you’ll run into problems. You can either remove the -, or use the beta version I uploaded here. This wasn’t a big enough problem for me to refresh the build.
Feedback is appreciated. Support is available on code.google.com.
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.
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.
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.
One of the questions I get asked a lot is how to integrate a CCK package into a Firefox distribution or install a CCK into an existing Firefox installation. This post will detail various ways to do that. All of the information I’m about to give applies to all add-ons.
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.
With all the discussion around Firefox in the enterprise, I hadn’t thought about mobile browsing in the enterprise. Apparently there is a company that has –
Is this something any Firefox enterprise users are hearing about?