Comment by hd4
It's advisable to use a prefs.js for this sort of thing
It's advisable to use a prefs.js for this sort of thing
Mozilla suggests policies [1] (which, in turn are capable of default-setting or enforcing most prefs and has proper release notes) and has removed a bunch of pages that previously recommended directly editing prefs.js or shipping user.js (which had been changed in backwards-incompatible ways before when the parser was swapped).
prefs.js is modified by browser itself. And it contains lots of stuff by default already.
You can store your custom preferences in user.js file - Firefox will copy those to prefs.js at startup.
From your link:
[1] https://kb.mozillazine.org/User.js_file