-
-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
armagadd-on 2.0: Mozilla's legacy hot-fix for Firefox 52 through 60: feedback from users of Waterfox 56.2.9 #956
Comments
To the anonymous person who found no difference after adding Mozilla's extension: can you describe your situation? If not here (maybe you have no GitHub account) then you might add a comment under https://redd.it/bnblfe Thanks |
The extension approach ONLY works for Waterfox 56.2.9 Desktop, NOT for Waterfox 56.1.0 Android! I have uploaded the certificate to my server with the correct MIME type and compiled a write-up how to import the certificate which works for both. You can find it here. |
Mozilla bug 1551289 - publish armagadd-on 2.0 hotfixes on AMO for self-install - to versions 52-56
Thanks to those of you who tested and responded to the poll. All six of you! (I was two of the eight voters.) |
@grahamperrin : https://addons.mozilla.org/en-US/firefox/addon/disabled-add-on-fix-52-56/ working in Waterfox Android 56.1.0 fresh virgin account: the add-on installs, is NOT and can NOT be enabled in Add-ons (even after WF force-quit and re-launch), but affected Add-ons DO nevertheless install. When force-quitting WF, remove cert9.db, re-launch WF, questionable Add-ons again do NOT install as before. Did some more tests [..] - in short, this hotfix WORKS even for WF Android. It installs the certificate then disables itself. NOT immediately working for Waterfox Desktop 56.2.9: "This add-on is not compatible with your version of Firefox" due to Waterfox pretending to be Firefox 57 on AMO in about:config?filter=general.useragent.override (credit to laniakea64 for the hint). It can however be downloaded manually, be dragged into about:addons and is even active. In a fresh virgin account, affected Add-ons DO then install. |
This is due to Waterfox pretending to be Firefox 57 on AMO, and this addon not being compatible with Firefox 57. You could also right-click the greyed out "Add to Firefox" button > Copy link location, then right-click Waterfox address bar > Paste & Go.
What method were you using to change user-agent? Changing the value of |
oh, you are right! I was using User Agent Switcher and Manager v.0.2.8. In older versions it would overwrite settings in about:config?filter=general.useragent.override, but v.0.2.8 acknowledges them and treats them superior. Thanks for the correction! However keeping that setting on 57 UA would most likely mean a regression in regards to the # of extensions that can be installed (most of which seem to be working fine in WF even though Mozilla would like them to only work in Quantum versions of FF), so I will keep that setting on UA 56. Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:57.0) Gecko/20100101 Firefox/56.0 |
Please see https://www.reddit.com/r/waterfox/comments/boazxg/-/ene52ae/ – there's a direct link to Mozilla's extension. |
To users of Waterfox 56.2.9 whose profiles may be bitten by Mozilla armagadd-on 2.0
If your interest is in the forthcoming update to Waterfox:
If you would like to add Mozilla's hot-fix to Waterfox 56.2.9:
– please do not address Waterfox feedback to Mozilla.
If you're new to Waterfox, it may help to know that historically, Waterfox 56.0 was based on Firefox 56.0.2.
Mozilla's hot-fix: a test routine for users of Waterfox 56.2.9
about:addons
(Add-ons Manager) please make a written note of the name of any extension that has a red alert (… could not be verified for use in Waterfox and has been disabled) – most users will find no such alertFor step (2) above, if you can not easily find an extension that is bugged by the download-specific red alert, try this one:
The text was updated successfully, but these errors were encountered: