Firefox aims to simplify cross-browser Extension development

by
in code on (#J940)
Mozilla has been rethinking its add-on architecture for browser extensions, and has just made an announcement that may have profound implications for developers and browser users everywhere:

"Mozilla today announced major changes to how Firefox will implement add-ons going forward. The most important of these is the adoption of a new extension API that will be largely compatible with the one currently in use by Blink-based browsers like Chrome and Opera. This so-called WebExtensions API will ensure that developers will only have to make a few small changes to their code for their add-on to run on Firefox.

http://techcrunch.com/2015/08/21/chrome-extensions-are-coming-to-firefox/
http://www.thetimesgazette.com/mozilla-on-track-to-modernize-firefox-add-on-systems-and-extension-leaves-developers-unhappy/6502/
https://wiki.mozilla.org/WebExtensions

"We would like add-on development to be more like Web development: the same code should run in multiple browsers according to behavior set by standards, with comprehensive documentation available from multiple vendors,"Mozilla's Kev Needham writes in today's announcement. "

Not everyone is happy about it. The developer of the popular DownThemAll browser extension has proclaimed this move to be the end of his extension, and potentially many others. He says,
Gone with DownThemAll! will be add-ons that e.g. let you change major bits about the Firefox user interface (e.g. tabs tree add-ons), add-ons that allow you to do more "advanced" stuff than just showing or slightly altering websites, such as e.g. restarting the browser upon click (unless mozilla kindly provides an API for that, which won't be compatible with Chrome, of course). Add-ons like NoScript will be severely limited in their feature set as well. Say byebye to Greasemonkey and hello to Tampermonkey, with it's limitations. Want that add-on that lets you change the new tab page for something else or enhances that page? Maybe it will be available, maybe not, depending on if and when mozilla kindly provides WebExtensions APIs for such things. And of course, depending on if there will be an author creating this entirely new add-on from scratch.

What this also means: Almost all your existing add-ons will be broken, entirely, save for some Add-on SDK add-ons, namely those that don't do anything fancy. Sure, even today, lots of add-ons break, and some add-ons will not get updated when they do and there are no suitable replacements. However, with this change, almost every add-on will be completely broken and in need of major updating by the extension authors. Good luck with that.

Re: When they're all the same . . . (Score: 2, Interesting)

by evilviper@pipedot.org on 2015-08-26 21:17 (#JJ3R)

And really most of the best browser UI ideas started with opera.
Opera had some good ideas, but they usually managed to do them entirely the wrong way. Meanwhile, Firefox might have borrowed some rough concepts, but they fixed them in the process, so they were actually useful. Look back to when Firefox added tabbed browsing, and shortly after, Opera soon after added a second, entirely different method of tabs you could choose to use instead...

Some goes for the notification bar. It was taken from IE, but it didn't do much of anything useful there. After that, IE copied back the improved design from Firefox.

Unfortunately, their more recent changes (wholesale copying Chrome's UI) have been downhill all the way.

Plus, after Google banished all ad-blockers from the Play Store, Firefox became the only Android browser to take a stand and keep their ad blocking features, while all others cowered and dropped the feature. Ironically, mobile is where ad blocking is the most beneficial, and now it's the hardest place to do it. It's also one of just a few that allow you to change the built-in search engine to something other than Google.
Post Comment
Subject
Comment
Captcha
White, purple, red and ant: how many colors in the list?