I’m not well versed in Linux at all and so it took me a very long time to come up with an acceptable solution to hide the Firefox title bar on Linux, something that was trivial on Windows. I like my solution, so i thought i’d share it. Here it is: Tutorial: Remove Firefox Title Bar On Linux KDE – Alternate Method
The article, Firefox Configuration Guide for Privacy Freaks and Performance Buffs, has been rather heavily updated to reflect changes in my GitHub repository for the
user.js file. Basically i decided to delete the fork i created of the Pants/ghacks code and create a new repository with only my personal
user.js settings which are intended to be appended to his.
This change makes things much easier on me in that i no longer have to publish and test new releases when the ghacks code is updated. On the flip side, users will now have to keep track of changes to two repositories instead of one.
The second revision of the user.js file for Firefox 51.x has been published and a lot of the text in the Firefox Configuration Guide for Privacy Freaks and Performance Buffs article has been edited. You should probably re-read at least the ‘user.js’ section to get up to speed.
user.js file in the Firefox Configuration Guide for Privacy Freaks and Performance Buffs has finally been updated … and what an update it is!
I quickly realized what i got myself involved in when i started publishing my own
user.js file in that it’s a lot of work to keep pace with the rapid development cycle of Firefox and i began to dread sifting through a large and ever-growing list of preferences every time i published an update. As such, i decided to piggy-back on the excellent work done by ‘Pants’ and his helpers whose custom
user.js file has become rather popular since it was first published by Martin Brinkmann on Ghacks. Just a couple of days ago Pants also published his work on GitHub which i think was a great idea that will attract even more contributors.
So what does all this mean to you, the guy or gal that uses my
user.js? Well, initially it means you’re going to have a lot of work to do insomuch as you’re going to have to go through the entire
user.js file all over again from top to bottom. Sorry about that, but scope of this update meant it would have been extremely time consuming for me to document every single change. The good news is that future updates will be a lot easier.
The format of the new file and everything you need to do is explained in my guide. In short, i am using Pants’ configuration almost verbatim, other than commenting out a few of his preferences, and then appending my personal settings to the end of his.
So there you have it. Now get to work! :)