Mozilla Firefox 57 - Compatibility Milestones

Page 1 of 4 123 ... LastLast
    Mozilla Firefox 57 - Compatibility Milestones

    Mozilla Firefox 57 - Compatibility Milestones


    Posted: 17 Feb 2017

    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:


    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.


    Source: https://blog.mozilla.org/addons/2017...ty-milestones/
    Brink's Avatar Posted By: Brink
    17 Feb 2017


  1. Posts : 46
    Windows 10
       #1

    No addons, no Firefox.
      My Computer


  2. Posts : 27,157
    Win11 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       #2

    Placebo said:
    No addons, no Firefox.
    Yep they're shootin' themselves it the foot, and will loose a big portion of their market share
    They are definitely not the safest browser out there, but... people use them for the add-ons(which actually slow browsing down by the way, but functionality over speed is ok, you need speed, then use Edge)
    But there are definitely add-ons that increase productivity, and that will be lost, or my favorite, the eye candy will be gone.
    FF was only my 3rd go to browser, time to find a new one.
      My Computers


  3. Posts : 46
    Windows 10
       #3

    Well I don't use Firefox as such, Waterfox was my primary, Chrome second, I'm assuming that Waterfox will splinter off now and continue to support addons for a longer period, if not then Chrome will probably have to become my primary, some stuff about Chrome was always better anyway, inline translation for example (I live in Sweden where I don't speak Swedish and soon moving to Portugal where I don't speak Portuguese so inline translation is a big thing for me!). If all else fails there's also Pale Moon which has some nice qualities.
      My Computer


  4. Posts : 2,935
    Windows 10 Home x64
       #4

    These are really bad news. FF without extensions isn't FF at all. I don't like Chrome so I will have to look out for an alternative.
      My Computer


  5. Posts : 46
    Windows 10
       #5

    eLPuSHeR said:
    These are really bad news. FF without extensions isn't FF at all. I don't like Chrome so I will have to look out for an alternative.
    Check out Waterfox: Waterfox - The best 64-Bit browser on the web
      My Computer


  6. Posts : 129
    W10
       #6

    Since they started these changes I have had to take FF off two laptops as it was always locking up. Both W10 but different users and with both I failed to find the problem.
      My Computer


  7. Posts : 7,128
    Windows 10 Pro Insider
       #7

    I wasn't happy with some of the changes they've already made so I switched to Pale Moon as my daily browser awhile ago. With the changes there planning I guess it's time to uninstall Firefox.
      My Computers


  8. Posts : 10,311
    Wndows 10 Pro x64 release preview channel
       #8

    I've used Firefox since version 3 and like it.
    Currently I only use three extensions so guess I'll just keep checking out the new dev builds and see what the outcome is.
    Currently running FF version 52 beta 7 and 53 latest dev build.
      My Computer


  9. Posts : 129
    W10
       #9

    I tried waterfox and its not locking up as the latter versions of Firefox were. Now added all the plugins we use and still OK.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:18.
Find Us




Windows 10 Forums