Windows 10: Timeline for disabling Firefox legacy add-ons on addons.mozilla.org

Brink · Aug 22, 2018

Mozilla will stop supporting Firefox Extended Support Release (ESR) 52, the final release that is compatible with legacy add-ons, on September 5, 2018.

As no supported versions of Firefox will be compatible with legacy add-ons after this date, we will start the process of disabling legacy add-on versions on addons.mozilla.org (AMO) in September. On September 6, 2018, submissions for new legacy add-on versions will be disabled. All legacy add-on versions will be disabled in early October, 2018. Once this happens, users will no longer be able to find your extension on AMO.

After legacy add-ons are disabled, developers will still be able to port their extensions to the WebExtensions APIs. Once a new version is submitted to AMO, users who have installed the legacy version will automatically receive the update and the add-on’s listing will appear in the gallery.

For more information about porting legacy extensions to the WebExtensions API is available on MDN. We encourage legacy add-on developers to visit our wiki for more information about upcoming development work and ways to get in touch with our team for help.
Click to expand...

Source: Timeline for disabling legacy add-ons on addons.mozilla.org | Mozilla Add-ons Blog

:)

PCpraiser100 · Aug 22, 2018

Mozilla Firefox Turns Five

Firefox deserves more than comments. Keep on the suggestions and forums on Mozilla ppl!

Aileen Alf · Aug 22, 2018

Slow Mozilla Firefox on Windows 10

Have you tried the suggested solution, changing your settings to High Performance? If you did and the issue still persists, we suggest that you check if you have the latest version of Mozilla Firefox.

To optimize your browsing performance when using Mozilla Firefox, you may try to disable or remove add-ons. Add-ons can sometimes cause browsers to run slowly and crash, or they might pose a security or compatibility risk.

Keep us in the loop.

Brink · Aug 22, 2018

Mozilla Firefox 57 - Compatibility Milestones

Back in November, we laid out our plans for add-ons in 2017. Notably, we defined Firefox 57 as the first release where only WebExtensions will be supported. In parallel, the deployment of Multiprocess Firefox (also known as e10s) continues, with many users already benefiting from the performance and stability gains. There is a lot going on and we want you to know what to expect, so here is an update on the upcoming compatibility milestones.

We’ve been working on setting out a simple path forward, minimizing the compatibility hurdles along the way, so you can focus on migrating your add-ons to WebExtensions.

Legacy add-ons
By legacy add-ons, we’re referring to:

All extensions that aren’t WebExtensions. Specifically: XUL overlay extensions, bootstrapped extensions, SDK extensions, and Embedded WebExtensions.

Complete themes. These add-ons shouldn’t have problems with multiprocess compatibility but will follow the same compatibility milestones as other legacy add-ons. We will provide more details on what’s coming for themes very soon in this blog.

Language packs, dictionaries, OpenSearch providers, lightweight themes, and add-ons that only support Thunderbird or SeaMonkey aren’t considered legacy.

Firefox 53, April 18th release

Firefox will run in multiprocess mode by default for all users, with some exceptions. If your add-on has the multiprocessCompatible flag set to false, Firefox will run in single process mode if the add-on is enabled.

Add-ons that are reported and confirmed as incompatible with Multiprocess Firefox (and don’t have the flag set to false) will be marked as incompatible and disabled in Firefox.

Add-ons will only be able to load binaries using the Native Messaging API.

No new legacy add-ons will be accepted on addons.mozilla.org (AMO). Updates to existing legacy add-ons will still be accepted.

Firefox 54-56

Legacy add-ons that work with Multiprocess Firefox in 53 may still run into compatibility issues due to followup work:

Multiple content processes is being launched in Firefox 55. This enables multiple content processes, instead of the single content process currently used.

Sandboxing will be launched in Firefox 54. Additional security restrictions will prevent certain forms of file access from content processes.

Firefox 57, November 28th release

Firefox will only run WebExtensions.

AMO will continue to support listing and updating legacy add-ons after the release of 57 in order to have an easier transition. The exact cut-off time for this support hasn’t been determined yet.

Multiprocess compatibility shims are removed from Firefox. This doesn’t affect WebExtensions, but it’s one of the reasons went with this timeline.

For all milestones, keep in mind that Firefox is released using a “train” model, where Beta, Developer Edition, and Nightly correspond to the future 3 releases. You should expect users of pre-release versions to be impacted by these changes earlier than their final release dates. The Release Calendar lists future release dates per channel.

We are committed to this timeline, and will work hard to make it happen. We urge all developers to look into WebExtensions and port their add-ons as soon as possible. If you think your add-on can’t be ported due to missing APIs, here’s how you can let us know.
Click to expand...

Source: https://blog.mozilla.org/addons/2017...ty-milestones/

Windows 10: Timeline for disabling Firefox legacy add-ons on addons.mozilla.org

Timeline for disabling Firefox legacy add-ons on addons.mozilla.org

Timeline for disabling Firefox legacy add-ons on addons.mozilla.org

Timeline for disabling Firefox legacy add-ons on addons.mozilla.org

Timeline for disabling Firefox legacy add-ons on addons.mozilla.org - Similar Threads - Timeline disabling Firefox

Cannot Add Firefox Add-ons to Toolbar or Overflow

Cannot Add Firefox Add-ons to Toolbar or Overflow

Firefox And Add ons

Mozilla response to recent Firefox broken add-ons error

Mozilla is aware of a bug that disables all Firefox add-ons (extensions)

Enable or Disable Extensions in Mozilla Firefox

Firefox Addon

The Future of Developing Firefox Add-ons

Firefox Add-ons attacked