Once that has been achieved, mobile browsers will follow. Mobile browsers are also in the pipeline, but are dependent on us having our own Sync service primed. The idea behind this change is that not only will Waterfox be incredibly performant, but also be at the forefront of supporting the latest HTML standards. If our features apply cleanly each release, we will then stop tracking the Extended Support Releases and instead start a rolling release for Waterfox. Over the next few months we will track the central branch of Gecko. We have also changed the way we make changes to the underlying Gecko platform, meaning we can now track releases faster and in a more automated way. Windows and Linux ARM builds will also follow in due course. Unfortunately this means we have to leave older systems behind - but any computer from the last decade should work.ĪRM builds are now available for macOS and these are also optimised, taking advantage of the new hardware Apple has to offer. We have aggressively optimised Waterfox for as much performance as possible. Waterfox has returned to its roots with performance at the forefront. We will be optimising the website over the next few weeks as well as setting up redirects for any old pages that have been missed. This website also allows us to add documentation, support documents and better ways to convey information. You may have noticed a new website - much more information, with a more practical structure. After enough time has elapsed, the automatic update will be seeded out to all users. Today marks the soft release of the 4th Generation of Waterfox. We will let you know when this is complete.

Over the next week, infrastructure will be put in place for Classic to keep it running properly. This will keep Classic ongoing for as long as possible - but the success of this project will still rely on contribution.

An organised, clear list of what security patches haven't been fixedĪ fair warning will be presented to all those who want to use Classic, that it may be vulnerable to multiple security issues - but the choice is given to the user to proceed at their own discretion.

Issues can be opened in a separate tracker, not getting closed for not focusing on G4.

Waterfox Classic will have its own simple landing page.

GitHub Actions will be clearly segregated, allowing easy viewing of ongoing builds.

Contributors can clearly see what Classic development is ongoing.

This has the following benefits by not having two versions of Waterfox sharing resources: To make sure the projects aren't falling over each other, Waterfox Classic will now be moved out of the main Waterfox development repository and into its own separate repository - updating the previously archived 'Waterfox Old', now named Waterfox-Classic. Unfortunately, due to the rapid nature that the web is now expanding at, keeping Classic up to date with that is difficult. G4 has its eyes set to the future - a modern browser, focusing on modern web compatibility without sacrificing speed, or the balance of privacy and usability.Ĭlassic has focused on keeping the tried but tested available. The version # of Waterfox browser is: 56.2.6 (64-bit).Since Waterfox Classic and Waterfox Current (now G4) diverged, they have both have separate goals. The version # of my add-on downloaded is: fireftp-2.0.4-fx.xpi I see no way to specify/configure a (new) account, with the connection-info to communicate with a web-server. The exact symptom is that the dropdown in upper left corner of the FireFTP tab says: '(Choose an account)', but clicking on that does nothing. NOT get FireFTP to create the account needed to connect to my (Formally, I used FireFTP addon under FireFox browser, but approx a year ago, due to revised architecture of Firefox, the FireFTP addon no longer is compatible with Firefox, and the suggested fix/workaround is to use the Waterfox browser, since Waterfox IS compatible with Waterfox.)īut, on the new laptop, for some unknown reason, I can get FireFTP addon downloaded, and installed upon Waterfox browser, but I can I install Waterfox browser solely because I've come to know and love the FireFTP add-on, for uploading web content to a web-server. On both laptops, I have Chrome as my primary browser, along with Opera and Firefox, and Edge all operational (I'm a web developer and test web-pages on the various browsers). So, I recently purchased a new laptop, with Windows-10 64-bit pre-installed.

A year or more ago, I first downloaded, installed, and had FireFTP addon working fine under the Waterfox browser, on a 5-year-old laptop, running Windows-10 64-bit.

Waterfox 47