Skip to content
This repository has been archived by the owner on Mar 24, 2022. It is now read-only.

firefox 57 #23

Open
koullis22 opened this issue Nov 15, 2017 · 7 comments
Open

firefox 57 #23

koullis22 opened this issue Nov 15, 2017 · 7 comments

Comments

@koullis22
Copy link

so what now? do we stay in 56 or is there any way to make it working on 57?

@Loirooriol
Copy link
Contributor

If you install Firefox 57 Nightly or Developer Edition, then you will be able to enable legacy extensions. See https://wiki.mozilla.org/Add-ons/Firefox57#Prefs

But the add-on released by ewwink won't work properly, you will need to add my patches. For Firefox 58 see my fork for additional patches, but there is recent issue I haven't fixed yet.

@koullis22
Copy link
Author

thank you for your reply...as i understand those 2 versions are more likely like tests and send feedback..
-is there a way to disable it?
-normal ff57 doesnt have those 2 options that need to work?
-as a normal ff user what would be better?

@Loirooriol
Copy link
Contributor

No, in Firefox 57+ Release and Beta it's not possible to install legacy extensions, unless they are signed by Mozilla internally.

See https://www.mozilla.org/firefox/channel/desktop/

  • Firefox Nightly is updated everyday with the latest features, and thus is less stable. It's two versions ahead of Release.
  • Firefox Beta is more stable than Nightly but less than Release. It's one version ahead of Release.
  • Developer Edition is like beta but with some additional features for developers, like allowing legacy extensions.
  • There is also ESR. Targeted for organizations, it's even more stable than Release.

So as a normal user you should probably choose one of

  • Use Firefox 52.x ESR, and stay in the 52.x branch even after Firefox 59.x ESR is released. Note the support for 52.x ESR will end when Firefox 61 is released, scheduled on 2018-07-03 (see calendar). At that point you should choose another option.
  • Use Developer Edition and enable legacy extensions. But the extensions may require some fixes.
  • Replace Firefox with some fork which does not block legacy extensions (maybe Waterfox or Palemoon?). But the extensions may require some fixes.
  • Give up using legacy extensions.

@koullis22
Copy link
Author

thanks for your clear answer:) and 1 last choice is just to install normal version 57 and install v4

@jeroen1956
Copy link
Contributor

jeroen1956 commented Nov 15, 2017 via email

@Loirooriol
Copy link
Contributor

Oriol, can you post this on the forum?

Done! http://xnotifier.tobwithu.com/dp/node/3645

@jeroen1956
Copy link
Contributor

jeroen1956 commented Nov 15, 2017 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants