
The only thing yet to try is to make a separate autoconfig file for my home users. This makes it a bit harder to troubleshoot (However, in this case the contents of the failover.jsc file are the same as the autoconfig file.)

I have noticed when you make an error in the autoconfig file that firefox doesn’t pick up on any changes, and maybe uses the failover.jsc file in the profile directory. It’s just as if the script does not reach the ‘else’ part. I’m not seeing any error, the default homepage is just the site, when that GCE system variable is set to 0. You can use a data URL to fake the complex preference behavior:ĭefaultPref("", "data:text/plain,=") Īnd that’s how you set the default value of the Firefox homepage with AutoConfig. So here is the million dollar question how do you set the default value for these preferences? There are some other ones in firefox.js, but these are the important ones. The complex preferences you’ll probably care about are: You need to be aware of all of the complex preferences in Firefox because if you want to set the default value of any of them, you’ll need to follow the instructions I’ll give later in this post. In the past, the Firefox homepage was localizable that’s why it ended up being a complex preference. So why is the browser homepage a complex preference? Complex preferences are used when you want to be able to translate a preference value. Pref("", "chrome://branding/locale/browserconfig.properties") įrom there, we can look in browserconfig.properties to see the value: To see the true value, we can look in the configuration file for Firefox:

Although when you go to about:config and search on and see about:home as the value, that is not the true value of. So what’s unique about the preference that it’s default values cannot be set like other preferences in the autoconfig file?Ĭomplex preferences are preferences whose default value is a pointer to a properties file that contains the value of the preference. This post should clear things up (and show you how to make it work). Recently I’ve seen a lot of questions around why defaultPref in an autoconfig file doesn’t work to set the Firefox hompage.
