4 ms·

It's probably better to go straight to the blog post about the migration: https://hackademix.net/2017/11/14/double-noscript/ https://hackademix.net/2017/11/14/

It's probably better to go straight to the blog post about the migration: https://hackademix.net/2017/11/14/double-noscript/ https://hackademix.net/2017/11/14/double-noscript/ Basically, the work to adapt NoScript and correspondingly expand the WebExtensions API has been going on for years, the original plan was to have a smooth transition when Firefox 57 came out, but there were some delays in the final days leading up to the release. Not recommended to stay on Firefox 56 because it won't get security patches; move to 52 ESR instead.

shock 9y ago
Moving to Firefox 52 isn't really an option for me because it's a pig compared to 55/56 (it consumes almost 5GBs of RAM compared to 1GB for 56).
- sp332 9y ago
  I think you can switch to an unbranded build of 57, and enable legacy addons. https://wiki.mozilla.org/Add-ons/Extension_Signing#Latest_Builds https://wiki.mozilla.org/Add-ons/Extension_Signing#Latest_Bu... You could also install the Developer Edition or a Nightly build. They're slightly less stable (usually pretty good for me) but they have the same option. https://www.mozilla.org/en-US/firefox/channel/desktop/ https://www.mozilla.org/en-US/firefox/channel/desktop/
  - sebazzz 9y ago
    > enable legacy addons Does that mean the XPCOM system has just been flagged as disabled, but not been removed yet?
    - sp332 9y ago
      As far as I know, yes. Firefox has already decided to transaction away from XUL, so the extensions will break eventually. It's just a question of when the particular APIs your extension relies on get removed.
    - bzbarsky 9y ago
      Various stuff has been removed. Other things have not been removed yet. You can see https://bugzilla.mozilla.org/showdependencytree.cgi?id=1347507&hide_resolved=1 https://bugzilla.mozilla.org/showdependencytree.cgi?id=13475... for a non-exhaustive list of things that can definitely be removed but haven't been yet.

shock 9y ago

Moving to Firefox 52 isn't really an option for me because it's a pig compared to 55/56 (it consumes almost 5GBs of RAM compared to 1GB for 56).

sp332 9y ago
I think you can switch to an unbranded build of 57, and enable legacy addons. https://wiki.mozilla.org/Add-ons/Extension_Signing#Latest_Builds https://wiki.mozilla.org/Add-ons/Extension_Signing#Latest_Bu... You could also install the Developer Edition or a Nightly build. They're slightly less stable (usually pretty good for me) but they have the same option. https://www.mozilla.org/en-US/firefox/channel/desktop/ https://www.mozilla.org/en-US/firefox/channel/desktop/
- sebazzz 9y ago
  > enable legacy addons Does that mean the XPCOM system has just been flagged as disabled, but not been removed yet?
  - sp332 9y ago
    As far as I know, yes. Firefox has already decided to transaction away from XUL, so the extensions will break eventually. It's just a question of when the particular APIs your extension relies on get removed.
  - bzbarsky 9y ago
    Various stuff has been removed. Other things have not been removed yet. You can see https://bugzilla.mozilla.org/showdependencytree.cgi?id=1347507&hide_resolved=1 https://bugzilla.mozilla.org/showdependencytree.cgi?id=13475... for a non-exhaustive list of things that can definitely be removed but haven't been yet.