These changes are expected to go live this week. The announcement also says that Waterfox Classic will have its own page on the official site, this is something which has bothered some users, as the lone mention of it, has been the link to the releases page, from which you can download the browser. A list of unpatched security issues will be made available on the browser's website. The developer says that Waterfox Classic's future will rely on contributions, by which he probably means what he previously mentioned, about porting security fixes from Firefox ESR.

And since it is no longer tied with G4, issues won't be closed because of complications/incompatibilities with the modern version. Now that Waterfox Classic has its own Github repository, users will be able to track and report issues related specifically to it. But more importantly, this will improve the development process of the browser, because previously, issues related to both versions were tackled together.

Firstly, users who relied on it will get new versions. This is a welcome move for multiple reasons. The developer cites that it has been difficult to keep the browser up to date with the main project, which is why the two variants have been diverged.

Kontos has confirmed that Waterfox Classic will continue to be supported, but it will exist as a separate open-source project from Waterfox G4. Waterfox Classic development will continue No wonder users started worrying, but if you were among them, you can rest assured that it is still being worked on. He had mentioned that its future depended on the ease of porting security fixes from Firefox ESR. Alex Kontos, the developer of the popular Firefox fork, had previously hinted that the Waterfox Classic version was not a priority.

Waterfox Current G5.1.10 for ios instal