#Waterfox addons install
#Waterfox addons update
#Waterfox addons Patch
#Waterfox addons upgrade

There are issues installing bootstrapped addons, resulting in an 'addon is corrupt' error message.

Multi-process mode (e10s) is not supported.

#Waterfox addons install

In order to install it into Firefox release or beta, you need to disable the extensions signing requirement.

Addon version numbers are not displayed next to their title in about:addons. This add-on has been tested with the following browsers (in alphabetical order): Basilisk RC1+, Firefox ESR 45-52, Firefox 45-58b, Pale Moon 27+, SeaMonkey 2.40+ and Waterfox 55+.

The status bar does not include default items (zoom, full screen, screenshot).

There are now additional preferences in about:preferences#privacy.

DNS-over-HTTPS is now disabled by default - you must opt-in if you wish to use it.

You can now toggle to populate extension information in about:addons.

When you open a 'New Window', the address bar will now focus correctly.

Modified 'Recent Activity' settings will now apply.

#Waterfox addons update

A February 2021 update to Waterfox enabled Chrome Extension Support. What's more is that the 'Classic' version of Waterfox is compatible with legacy Firefox add-ons - specifically, from the pre-quantum (2016) days.

about:preferences no longer renders incorrectly in certain situations. One of the biggest draws for Waterfox is that it's compatible with the vast majority of Firefox add-ons.

The Waterfox Classic styled theme 'Australis' is now available! You can switch to it in about:addons → 'Themes'.

If you started creating new sessions and logins in G4 and would like to have them still used, you can type about:config in the address bar, search for and toggle it to true once more. In G4.0.1 it is now OFF by default and your previous G3 session will be restored.

This privacy focused preference only allows cookies, cache and local storage accessible by websites on the same domain and creates a separate session to when it is disabled. This was due to the setting of First Party Isolation to ON by default. This enables you to see and understand how we are building Classic, and of course join the community and help improve Classic. Open Source Contributing to Waterfox Classic Waterfox Classic is open-source and MPL2 licensed.

#Waterfox addons Patch

The add-ons can also be installed in Waterfox versions that are affected by the issue as well to patch the issue in the third-party browser.ONLY if you upgraded from G3 → G4.0.0, you may have had your login sessions on various websites unavailable. Waterfox Classic is based on an older version of the Gecko platform which allows the development of XPCOM and XUL add-ons.

The extension installs a new certificate and re-enables extensions and themes that were disabled. In Waterfox Classic, I can finally be efficient like I used to be several years ago and, being.

#Waterfox addons upgrade

For whatever reason those people are on those older versions, they are now not forced to apply the temporary workaround or upgrade to the latest version 66.0.5. I have just discovered Waterfox Classic Portable after a few years struggling with different browsers because so many websites stopped working on my previous, pre-WebExtensions version of Firefox, on which less and less of my favourite addons worked. Now though, and after pledging to release fixes for older and unsupported versions of Firefox, Mozilla has released add-ons that fix the certificate signing on Firefox 47 - 56, one for those on version 57 - 60, and lastly for versions 61 to 65.

While there were several workarounds that could be applied before Mozilla was able to issue a hotfix release in the early hours of Monday morning, which was followed up by another a couple of days later, this left those on older versions to search for a temporary workaround.

Around a week and a half ago on Saturday May 4, a certificate used to sign Firefox add-ons expired and subsequently blocked new add-ons from being installed and existing add-ons to stop working altogether.