Doing so breaks application updates whenever all.js must be updated (more details are given in bug 448504). This document previously recommended modifying the 'all.js' file in the greprefs subfolder.The local-settings.js file should be saved ANSI encoded.

Now, all of the prefs listed will be locked. Save the change and completely restart the application.Pref('_value', 0) // only needed if you do not want to obscure the content with ROT-13 Open the 'local-settings.js' file in a text editor and add the following line to the bottom, which points to the newly created lock file.Create a new file (eg 'local-settings.js') in the defaults/pref subfolder of the installation directory. As described in the about:config entries article, the setting to use a direct connection is 0.įinally, you must tell the application to load the lock file. If you search for 'proxy', you will eventually find the preference string for this option is ' '. Since it is commonly requested, we will use the browser proxy setting as an example.If all else fails, you can ask in the forums or on IRC.When the browser closes, it saves user-specified settings to the prefs.js file in the profile folder.Preference settings, both user-specified and default values, are displayed in the about:config window while Firefox or SeaMonkey is running (in Thunderbird you have to invoke the Config Editor from the Advanced preferences), Settings shown here are updated as you change them in the browser.A mostly complete list describing available settings can be found online on the about:config entries page (along with mail and news settings specific to Thunderbird and SeaMonkey).You must first determine which settings you want to lock.

Where are firefox extensions stored