Welcome to nsane.forums

Welcome to nsane.forums, like most online communities you need to register to view parts of our community or to make contributions, but don't worry: this is a free and simple process that requires minimal information. Be a part of nsane.forums by signing in or creating an account.

  • Access special members only forums
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates

Sign in to follow this  
Followers 0
Batu69

Firefox Add-ons Roadmap for 2017

3 posts in this topic

The year 2017 is an important one for Mozilla and Firefox. Multi-process will be enabled for all users of the web browser, sandboxing is introduced, the first bits of Project Quantum are integrated into the web browser, and the add-on system will be switched exclusively to WebExtensions.

 

Mozilla revealed an updated add-ons roadmap yesterday that highlights major milestones on the way to making Firefox WebExtensions exclusive.

We talked about Mozilla's plans for Firefox in this regard before. WebExtensions is a set of APIs that developers can utilize to create add-ons for browsers. Firefox is not the only browser to use WebExtensions, as others, Chrome, Opera and Edge, use the system as well.

 

That's good for cross-browser development, better for Mozilla's add-ons review process, better for add-on compatibility with future Firefox versions, and probably also better for browser stability.

Firefox Add-ons Roadmap for 2017

firefox addons 2017

 

WebExtensions is a good addition to Firefox, and most Firefox users who criticize Mozilla are not doing it because of the integration, but because of Mozilla's plans for the browser's legacy add-on systems.

 

Mozilla plans to cut all ties to those add-on systems. This means that legacy add-ons won't run in Firefox anymore when the plug is pulled.

Legacy add-ons, as defined by Mozilla, are all extensions that are not WebExtensions. This includes anything with XUL, bootstrapped extensions, SDK extensions, embedded WebExtensions, and complete themes.

 

Language packs, dictionary files, OpenSearch providers, lightweight themes, and add-ons that are exclusively available for Thunderbird or SeaMonkey are not considered legacy by Mozilla.

 

Any legacy add-on that is not ported by its author to WebExtensions -- if that is possible -- will no longer work in Firefox 57.

A big issue that developers face right now is that WebExtensions is a work in progress. Not all APIs are available yet, and some APIs that are required for certain legacy add-on features may never make it into Firefox.

 

This has caused some developers to quit development, or paint a grim picture in regards to the future of their add-ons.

The Roadmap

See Firefox release schedule for release dates.

Firefox 53: April 18, 2017

  • New legacy add-ons won't be accepted anymore on AMO (addons.mozilla.org). Updates to existing add-ons are still accepted.
  • Add-ons may only load binaries if they use the Native Messaging API.
  • Multi-process is on by default for all users. Only exception for systems with add-ons that state explicitly that they are not compatible with multi-process.

Firefox 54 to 56: June 13, 2017 to October 3, 2017

  • Mozilla launches multiple content process for E10s in Firefox 55 and security sandboxing in Firefox 54. This may impact some legacy add-ons.

Firefox 57: November 28, 2017

  • Legacy add-ons are no longer supported. Firefox won't load legacy add-ons anymore. Firefox 57 is WebExtensions exclusive-
  • Multi-process compatibility shims are removed from Firefox.
  • Legacy add-ons remain on AMO for the time being. Mozilla has yet to announce a deadline for end of support for these listings (the listings may still be updated for instance)

Closing Words

It is too early to conclude how the move will affect Firefox's add-ons ecosystem. Some developers announced that they won't migrate to WebExtensions already, and the same is certainly true for add-ons that are no longer in development but still working right now.

 

Some of these may be ported by other authors, and there will certainly be an increase of Chrome extension ports to Firefox. Also, most Chrome extensions will work in Firefox eventually when Firefox reaches parity with Chrome in regards to WebExtensions APIs.

 

WebExtensions will limit Firefox add-ons in regards to what they can do to the browser.

 

Article source

3 people liked / thanked this

Share this post


Link to post
Share on other sites

This will be the most addons have been effected since they changed to Google's  way of updating with Rapid Release updates  in 2011 and that didn't work out good and they changed there mind 5 years latter .

http://www.ghacks.net/2016/02/05/firefox-gets-a-variable-release-schedule/

All the work the addon devs done too keep up with them now Firefox is going  just knock many out of the picture , because many want even work as a  WebExtension by design . This will mark the end of a Era . It's a shame Firefox will move into Opera's shoes were a legacy version of there browser will be remembered as the last good version . But what do we expect from a company who failed once before in the 1st browser wars ?   When Mozilla was Netscape and Microsoft's IE beat  them into oblivion.  Once bitten, twice shy baby!

 

The people left on Firefox will be left on it just because it has the Firefox name and it want really be much better than the open source chromium browser/ Time too switch too SeaMonkey I guess  if we want too use old addos I dont hear then saying anything  about them migrating  too WebExtensions on it.

Edited by steven36
1 person liked / thanked this

Share this post


Link to post
Share on other sites

Looks like I stop at Firefox 52 and then sit back and see what happens.

 

Unless all the addons I need are compatible with Firefox versions after 52, I ain't movin'. Period.

 

Updating wouldn't be so bad except Mozilla still practices the dumb checking of addon compatibility AFTER updating Firefox, so it's "Congratulations, you have updated to the latest Firefox. Oh, by the way... these 3 addons that you need won't work anymore. Have a nice day".

 

Any responsible company with an ounce of sense, would check for addon compatibility BEFORE updating. Wait... silly me... what was I thinking... I forgot... keeping stuff up-to-date is paramount, whether I can use it or not isn't important...

3 people liked / thanked this

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0