I wonder if Waterfox devs would be willing to add back the unread tab status and the option to not fire the select-all action when the URL bar is focused, two other things Mozilla recently ripped out that have made it a much worse product than it was before in the way I use it. The main reason I ever needed them in the first place was to fix what Mozilla had done to Firefox! As long as I could revert the UI changes Mozilla made with each successive release, I didn’t mind too much that they’d made them.

If they add back all of the things Mozilla removed, it won’t even matter that the classic addons don’t work anymore.

This is a really promising direction for Waterfox. I’ve had the page zoom controls between the URL box and the search box since forever ago, and that made the one in the status bar redundant. Fortunately, a little bit of custom css in userChrome.css is able to get rid of it. As with Vivaldi’s status bar, the new Waterfox one has a page zoom control on the right side, though there’s no option to remove it that I was able to find. Vivaldi also has an optional status bar, but it’s not possible to put the addon icons in it. As with the original status bar and the one that the Classic addon Status-4-Evar added back in, it is possible to move the addon icons to the new status bar. I was able to do it with a custom stylesheet (same idea as userChrome.css), but having it available from the settings menu is far better.Īs if that wasn’t enough, they’ve also put the option to have a status bar back in. Even Vivaldi (which is meant to be a highly configurable browser that has every conceivable option) doesn’t have that, even though it’s been requested for a few years by now. I just took another look at the newest Waterfox, which is G3, and discovered that they’d implemented the much-requested option to put the tab bar between the content and the URL bar. Classic is not the only Waterfox… there’s also Waterfox Current and Waterfox G3.

I haven’t paid much attention to Waterfox since I moved on from Waterfox Classic. Fortunately, the custom CSS duplicates enough of the functionality of CTR to make Firefox look and behave much as I want it to. The weaker Chrome-style addons that (poorly) replaced the Firefox-type XUL/XPCOM addons couldn’t put back what Mozilla had removed. Of course, when the next thing that was lopped off of Firefox was the ability to use Firefox addons like CTR, that didn’t work anymore. In its never-ending goal to be Chrome, Mozilla had removed features from Firefox that many of us consider essential, and Custom Theme Restorer let us have them back. I used Waterfox (which turned into Waterfox Classic) for a few years after the release of Firefox Quantum, but as its internal feature set was frozen at the Firefox 56 level, I began to have issues with it not working with some sites, so I reluctantly went back to Firefox proper.įortunately, I’d discovered modifications to userChrome.css by Aris, the author of Custom Theme Restorer.

Waterfox classic theme restorer