#Revert to firefox 56 plus

Sadly, most change seems to be of that variety, in tech or otherwise.В вЂњChange is goodвЂќ is an aphorism that is wrong more often than not. It doesnвЂ™t matter what field of endeavor I am in, tech or otherwiseвЂ¦ change that makes things worse is bad. If it comes to pass, I will have to move on from Firefox. TheyвЂ™ve done this many, many timesвЂ¦ take a feature, turn it off by default, include a pref to turn it back on, then get rid of the pref. Now that the ability of Firefox to parse userChrome.css and userContent.css are off by default and hidden behind a pref, thatвЂ™s a clue that there are plans to get rid of it. Why, I remember, back in the day, when having a feature the other guy didnвЂ™t have was a good thing!

#Revert to firefox 56 plus

Chrome does not have user stylesheets, and the Mozilla philosophy of the last eight years plus has been that if Chrome does not have it and Firefox does, it must be eliminated. There is more than a trivial chance Mozilla will do that with the user stylesheets. Then, one day, one of those updates made Classic Theme Restorer stop working, forever. I used it to make Firefox look the way I wanted as Mozilla updated it again and again. That was precisely what I was doing with Classic Theme Restorer. It takes some time, but you can use this to make Firefox look the way you want as Mozilla updates the browser again and again. Keep very close track of the changes you make so you can reverse those you donвЂ™t like. Works a treat, though not nearly as easy to use as the extension had been.

I used Aris-T2вЂ™s вЂњClassic Theme RestorerвЂќ extension to get rid of Australis on Firefox <57 and Waterfox Classic, and now that I use Firefox proper, I use the stylesheets by the same author. (Australis, Photon, Proton, respectively). Yes, the new format annoys me! And so does the one after that, and the one after that.