Extension Update UI

If you're upgrading your users and you don't want the extension update dialog to show, just set the preference extensions.showmismatchUI to false.

The Return of Operator (sort of) and other Mobile Add-ons

I did a few add-ons for the Amp Your Firefox Contest. I was waiting to publicize them just in case I needed to beg for votes. Sadly, I don't.

The first one is Total Title. It allows you to easily see the full title text for images. It's primarily for comic sites like xkcd that hide additional jokes in the title attribute.

The second one is Site Shaker. If you go to a web site, you can shake your phone and it will take you to a random link on that site. It's a fun way to navigate through Wikipedia.

The third one is Operator Mobile. Using Glenn Jones' awesome microformat-shiv, I was able to implement microformat support on Firefox Mobile. It allows the export of contacts and calendar events to your mobile device, as well as the opening of addresses into whatever mapping app you are using. I'm investigating a new desktop version of Operator as well, but it's taken a back seat to other efforts. Hopefully I'll be able to put something together soon.

Enjoy.

Keyword Search Updated


Version 1.0.5 of Keyword Search is up.

It adds:

  • Setting the search engine for about:home
  • I'm Feeling Lucky support for Google
  • Browse by Name support for Google
  • I'm Feeling Ducky support for DuckDuckGo

I'm really trying to avoid adding support for custom URLs (like keyword.URL). I'd rather try to address the reasons why people need to use custom URLs. If there is some other reason you prefer to use a URL, please let me know.

I've also fixed a few bugs:

  • When you disabled the add-on it was still functional.
  • Using search engines with non English names didn't work.
  • Sometimes searches would go to the wrong window/tab.

I've had some reports of searches in other languages not working, but I haven't been able to recreate it. Honestly, this shouldn't happen because the method I'm using to invoke the search is the exact same method that Firefox uses when it does a keyword search. If you are able to recreate this consistently, I'd love to hear from you.

Keyword Search and Firefox 23

UPDATED: 1.0.2 adds support for POST search engines. You'll have to install it manually if you have 1.0, since non approved add-ons don't get updated automatically.

If you've been keeping up with the development of Firefox 23, you know that one of the big complaints is the change to keyword search. Starting with Firefox 23, searches in the URL bar will always use the search engine that is set in the search bar. So if you change your search bar to Wikipedia, and then do a search in the URL bar, it will use Wikipedia.

I've built an add-on that allows you to set the keyword search engine separately from the search bar. It can be any search engine you have installed. It's called Keyword Search and it's available from AMO.

Also note that this add-on includes DuckDuckGo as a recommended search engine. If you like the work I do, please consider trying it out and seeing if you like it.

Shameless Plug for TrackIF

This is a shameless plug for an add-on I worked on. It's called TrackIF. The way it works is that when you see a product you want to track the price of, you click the add-on button and add it to your tracker list. It will then notify you when the price drops or reaches a specific threshold. And it's not just about stores, you can track craiglist, eBay or even real estate.

The Firefox extension is available here.

CCK Wizard 1.4 Finally Available

I've finally released the official CCK Wizard 1.4. It will take a while to be approved, but you can download it from AMO now. Here are the changes:

  • Allows disabling sync and private browsing
  • Adds support for server ceritficates
  • Fixes a compatibility issue with Firefox 22
  • Allows empty strings to be locked
  • Adds support for whitelisting and blacklisting sites for plugins

It also removes support for Livemarks (If you need this, please let me know).

If the CCK Wizard saves you time and helps you deploy Firefox, please consider contributing to it's development by clicking here.

The CCK Wizard is maintained in Google Code. That's the place to report bugs. Also, please consider becoming a contributor.

Make Your Feature Enterprise Ready

When enterprises (and others) are customizing Firefox, I get asked pretty much the same questions every time:

  • How do I disable private browsing?
  • How do I turn off Firefox Sync?
  • How do I prevent access to about:config?
  • How do I prevent the installation of add-ons?
  • How do I prevent access to the add-ons manager?

Doing any of these things properly is actually quite difficult, because none of the people that developed these features ever thought that someone would want to disable them. I think the primary reason for this is that most people that create software have only ever experienced how one type of person uses a computer. They believe that everyone uses a computer like they do; they have full access to the computer, they can do whatever they want and they can customize the computer however they want. This narrow view causes them to create software for people like them.

The reality is that people use computers in many different ways. In many industries, organizations, governments and educational institutions, there is a need to prevent people from having too much access to the computer and the browser. And it's not just things like kiosks. It could be shared computers at a hospital or bank, or it could be simply that the employees are not very computer literate and you want to make sure they have limited access. Or maybe the browser is used on a piece of equipment and you want to make sure it can't be messed with. There are tons of reasons why someone would want to disable certain features.

Whenever you create a new feature, you should ask yourself this questions:

Is there a good reason why someone would want to disable this feature?

If the answer is yes, you should provide a single global preference that removes the entire feature. You should also ensure that when this preference is locked, any associated UI associated with that feature is disabled.

Asking this simple question before implementing a new feature will go a long way towards making sure Firefox is enterprise ready.