Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

cfg-files with FF65 RR not working with browser.startup.homepage

  • 1 reply
  • 1 has this problem
  • 2 views
  • Last reply by cor-el

Stingray-75
Stingray-75
more options

So, I am deploying the FF65, the RR version - somehow since FF62 there seems to be an issue with the cfg-files. Or did I miss something? I know that the ESR now supports the GPOs, but I am trying to use the latest version.

I have tried to use (i.e I have used "faz.net" for website):

ABC("browser.startup.homepage","https://www.faz.net"); ABC("startup.homepage_override_url","https://www.faz.net"); ABC("startup.homepage_welcome_url","https://www.faz.net");

whereas I used for ABC the listed parameters: lockPref DefaultPref Pref

None of those 3 sets work, the other settings are set. If I verify these settings on "about:config" the above listed entries show "about:homepage" and "about:welcome".

Would anyone of you be able to verify this please? Any ideas how to solve this? Thank you.

So, I am deploying the FF65, the RR version - somehow since FF62 there seems to be an issue with the cfg-files. Or did I miss something? I know that the ESR now supports the GPOs, but I am trying to use the latest version. I have tried to use (i.e I have used "faz.net" for website): ABC("browser.startup.homepage","https://www.faz.net"); ABC("startup.homepage_override_url","https://www.faz.net"); ABC("startup.homepage_welcome_url","https://www.faz.net"); whereas I used for ABC the listed parameters: lockPref DefaultPref Pref None of those 3 sets work, the other settings are set. If I verify these settings on "about:config" the above listed entries show "about:homepage" and "about:welcome". Would anyone of you be able to verify this please? Any ideas how to solve this? Thank you.

All Replies (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

The function names are case sensitive as is a requirement fir JavaScript. I think that lockPref() should work. The defaultPref() function call needs special handling for localized (complex) prefs.

  • defaultPref("browser.startup.homepage", "data:text/plain,browser.startup.homepage=https://www.faz.net"); 
defaultPref();	// set new default value, requires special data: format for localized prefs
pref();	// set pref, allow changes in current session
lockPref();	// lock pref, disallow changes

The autoconfig.js file in the "defaults/pref" folder (same folder as channel-prefs.js). 

//
pref("general.config.filename", "autoconfig.cfg");
pref("general.config.obscure_value", 0);

The autoconfig.cfg and autoconfig.js files need to start with a comment line (//).

See also: