Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

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.

Pelajari Lebih Lanjut

Does setting "browser.startup.homepage" during install lock keeping any user changed homepages?

  • 4 balas
  • 4 memiliki masalah ini
  • 2 kunjungan
  • Balasan terakhir oleh ragnar86

When I set the page using the pref command, using the common "mozilla.cfg" method, any time a user tries to set the home page, it does not save. Instead it reverts back to the page set by pref. I can see in the users pref file that it is being correctly written, however once Firefox is completely restarted, it resets this in both the Firefox options and the users pref file. Is expected behavior or is it an issue anyone else has encountered?

When I set the page using the pref command, using the common "mozilla.cfg" method, any time a user tries to set the home page, it does not save. Instead it reverts back to the page set by pref. I can see in the users pref file that it is being correctly written, however once Firefox is completely restarted, it resets this in both the Firefox options and the users pref file. Is expected behavior or is it an issue anyone else has encountered?

Solusi terpilih

Thanks for your help but that still did not resolve the issue. What I have ended up doing is to edit the browserconfig.properties file found in the omni.ja\chrome\en-US\locale\branding\ folder and then copying that down to the local path. All of my other modifications performed in the Mozilla.cfg file work without issue.

Baca jawaban ini dalam konteks 👍 0

Semua Balasan (4)

this is expected behaviour, pref() only allows changes during the open session

instead try defaultPref("browser.startup.homepage", "http://example.com");

Thanks for your solution. I tried applying the defaultpref, but it fails to work saying it cannot access the configuration file.

mind the capital letter in defaultPref, then it should work!

Solusi Terpilih

Thanks for your help but that still did not resolve the issue. What I have ended up doing is to edit the browserconfig.properties file found in the omni.ja\chrome\en-US\locale\branding\ folder and then copying that down to the local path. All of my other modifications performed in the Mozilla.cfg file work without issue.