Browser Changes and How They Affect Add-Ons
On March 14, 2011, Microsoft released Internet Explorer 9 (IE9). The look and feel changed with the information bar moving to the bottom of the browser and the search bar being integrated into the address bar. But overall, the change in user functionality is what affected add-ons the most. This change also created a very different experience for the user in terms of what they have to do to use add-ons after they install them.
IE9 asks for the user’s consent to enable newly installed add-ons, instead of automatically enabling them from the start:
When the user clicks Enable, they are shown this screen:
This could lessen the chance of the user actually being able to use the add-on that they installed. They may click Don’t enable or they may just X out of the message completely because they don’t understand what it is or they are annoyed by the messaging.
IE9 also gives the user information on what is slowing down their browser and messages them on a regular basis asking them to speed up their browser by disabling add-ons:
When the user clicks Disable add-ons, they are shown this screen:
If the add-ons the user has installed and enabled total a load time of more than .2 seconds, the add-ons will show up on this list and the user may choose to disable them. This new functionality helps speed up the user’s browser, but it can also cause the user to want to uninstall all add-ons listed whether or not they really contribute to slowing down their browser.
On November 8, 2011, Mozilla released Firefox 8 (FF8). This new version adds a new confirmation prompt for add-ons. This prompt is different depending on whether or not the add-on is installed via an XPI or an EXE.
When an add-on is installed via an XPI, FF8 displays a modal dialog box with an Install Now button:
The user has to click Install Now to enable the add-on(s). If they click cancel, the add-on(s) will not be enabled for use.
When an add-on is installed via an EXE, FF8 opens a new tab with a checkbox confirmation screen:
By default, the checkbox is not checked, so the user has to check the box next to Allow this installation and then click Continue to be able to use the add-on. If the user doesn’t check the box and clicks Continue, the add-on will not be enabled.
With the changes these new browser versions bring, it seems that the ultimate goal is speed. Each browser wants to be the fastest. These changes can be seen as both positive and negative for users. As a positive, users may have a faster browser and not have to wait as long for load times. As a negative, they have to take additional steps to “enable” add-ons that they have already agreed to install and in some cases, they have agreed multiple times through certain processes that confirm the user is installing what they want to install.
These changes can also be seen as both negative and somewhat positive for add-on developers. As a negative, these changes make it harder for an add-on developer because users have to take additional steps to be able to actually interact with their add-ons. As a positive, with survival becoming harder and harder for add-ons, it encourages developers to make sure their add-on has a fast load time and it creates enough value so the user will want to take the necessary steps to enable the add-on for use. However, even with those changes, it doesn’t ensure that the user will “enable” their add-on. Another alternative for add-on developers might be exploring the options of building out a desktop version of the add-on so the application isn’t affected by any of these changes.
Overall, sometimes change is good and sometimes it’s not so good. As things change though, we have to roll with those changes and allow ourselves to make the best of them. We will just have to wait and see what comes next! Do you have any tactics to deal with browser changes? If so, add them to the comments.
Nicole Virnig, Account Development Manager, W3i, LLC
Nicole focuses on growing W3i business relationships, making sure the client has what they need to make them successful. If they aren’t happy, she isn’t happy.







