Open ghost opened 6 years ago
Could be an additional option, just like lockprefs, see #40. Currently you should be able to use the prefs.js only download for this
Using the prefs.js should work fine but the easy way should be just to replace the label and link name of "Download only prefs.js". As I understand it it is much cleaner to use the user.js.
The question is, if you want to allow the user to permanently change the setting back. You may notice that your generated profile breaks to many things and reset some setting so it does not break them anymore. If you set it in user.js, you cannot reset it in about:config.
Okay, thats a big point.
Both have their value. Some people may want a user.js. For example you could make it read only and prevent extensions from permanently messing with your settings by using a users.js.
So I keep this bug open for Infrastructure and it may be worth looking at some option on the website to select which options should be prefs.js and which ones should be user.js.
http://kb.mozillazine.org/User.js_file
User.js could be used if someone wants to keep some of the settings of an already existing profile.
The user.js has to be placed in the profiles folder and will be applied when Firefox starts (and every time Firefox starts). The settings are simply integrated into the existing prefs.js. To make changes to the settings in user.js through about:config the user would have to change or delete the user.js file.
This is my understanding anyways and what I've figured from experimenting with it.
Offering it as an alternative to the prefs.js (or explaining that one can rename the file to user.js, start FF and then delete user.js to keep already existing configuration) could be useful for some.
What do you think?