Some legacy add-ons will stop working due to the two changes above.Firefox will expand multi-process support from two processes to three and more.Firefox will expand its sandbox security feature to include multi-process support.Legacy add-ons = Firefox add-ons built on the old Add-ons API, XUL overlay extensions, bootstrapped extensions, SDK extensions, and Embedded WebExtensions. Firefox will fall back to single-process if the user uses a multi-process incompatible add-on.Firefox add-ons confirmed as multi-process incompatible will be disabled in Firefox.Firefox will run with multi-process support for most users.
#FIREFOX ADD ONS UPDATE#
Developers and users will be able to update legacy add-ons.No new legacy add-ons will be accepted on (AMO).Set for release on April 18, this release marks an important point in the Firefox timeline. Just take into account that the current Firefox release is Firefox 51. Over the coming year, Firefox will be putting the finishing touches on a plan it set in motion in 2015, which was to replace the aging Add-ons API with a new system called WebExtensions, based on the same extensions API used by Chromium browsers such as Chrome, Vivaldi, Opera, and others.Īfter launching limited support for WebExtensions in August 2016 with the release of Firefox 48, Mozilla has slowly added new features in following releases, moving forward for full WebExtensions support.īelow are Mozilla's intentions regarding how Firefox will handle add-ons in 2017 and afterward, along with how multi-process (e10s) support will also factor into consideration.