Andy McKay, Engineering Manager at Mozilla, announced yesterday on the official add-ons blog that Mozilla would implement temporary add-on loading in its Firefox web browser.
Now why would the organization do such a thing? One major change to the add-on system of Firefox that hit Firefox 43 was the add-on signing enforcement.
All versions of Firefox ship with a switch that allows users to disable the enforcement so that they can load and run unsigned extensions in the browser. This will change in the future (likely Firefox 45) for Firefox Stable and Beta versions as Mozilla plans to remove that option from those browsers.
The change impacts not only users of the browser but also add-on developers. Considering that testing is a large part of the add-on creation process, not being able to test unsigned add-ons in Firefox Stable or Beta would seriously hinder and delay the development process.
Temporary add-on loading is Mozilla's solution to the problem. Starting with Firefox 45, Firefox will support an option to load an add-on temporarily in the browser.
The feature is aimed at developers who need to test their add-ons on Firefox Stable and Beta versions, but can be used by anyone using Firefox.
To load temporary add-ons in Firefox, do the following:
The selected add-on is added to Firefox automatically without installation prompt. It is listed under Extensions on the page, and will remain enabled for the length of the browsing session. Once you restart the browser, it is removed automatically again and won't be available anymore until you load it again in the browser.
The new temporary add-on feature bypasses the add-on signing restrictions that are in place in Firefox allowing you to load unsigned extensions in the browser.
Since add-ons are loaded only for the session, it is not really of use to Firefox users who want to keep on using unsigned extensions without switching to Firefox Developer Edition or Firefox Nightly.
One big issue of the approach that Mozilla has not mentioned is that the method won't work for add-ons that require a restart of the browser.
The solution is not ideal, and if Mozilla would look over at how Google handles these things, it should probably consider bringing Google's Developer Mode feature to Firefox instead. This would be far more developer and user-friendly than what is created right now.Advertisement
Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.
We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.
If you like our content, and would like to help, please consider making a contribution:
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.