Open Bug 685250 Opened 13 years ago Updated 2 years ago

Homepage does not default back correctly

Categories

(Firefox :: Settings UI, defect)

6 Branch
x86_64
Windows 7
defect

Tracking

()

UNCONFIRMED

People

(Reporter: shawn.constable, Unassigned)

Details

User Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; InfoPath.3; .NET4.0C; .NET4.0E)

Steps to reproduce:

I have a mozilla.cfg file working properly that constists of the following:

pref("browser.startup.page", 1);
defaultPref("browser.startup.homepage", "<Homepage URL>");
pref("startup.homepage_override_url", "<Homepage URL>");
pref("startup.homepage_welcome_url", "<Homepage URL>");
lockPref("browser.rights.3.shown",true);
lockPref("network.automatic-ntlm-auth.trusted-uris", "<Internal URLs>");
lockPref("network.negotiate-auth.delegation-uris", "<Proxy URL for NTLM auth>");
lockPref("network.negotiate-auth.trusted-uris", "<Proxy URL for NTLM auth>");
lockPref("network.proxy.type",5);
lockPref("browser.shell.checkDefaultBrowser",false);


Actual results:

For a new user everything works fine when they start Firefox for the first time - Homepage gets setup properly and everything works.

If the user changes their homepage to somethign else
Then changes it back to Default using the "Return to default" button
The homepage will no longer load in the browser when firefox starts up


Expected results:

The home page should have been returned to the default homepage as specified in the mozilla.cfg file
After some additional testing I have found the following to be true - 

Firefox starts the first time - homepage works as expected.
Firefox is closed
Firefox starts the second time (no changes were made) - Homepage does not load.
Can you try setting the defaultPref for homepage differently and see if that works?

See:

http://mike.kaply.com/2012/08/29/setting-the-default-firefox-homepage-with-autoconfig/
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.