293535 - update autoconfig js does not update userpref.js, cannot change proxy or homepage setting

Status: RESOLVED INVALID

(Firefox :: Settings UI, defect)

Description

[ozzy osbourne]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

I have a mozilla.cfg file that points to a web server which configures the 
proxy settings and default home page.  The config file/web server file 
configure the Firefox 1.03 browser perfectly but it you update the web server 
config file the update does not happen to the browser's users's pref.js file.

I can delete the failover.jsc and the pref.js file in the user profile and the 
correct setting will come down.

What are the correct settings to make the firefox browser look at that site 
each time the browser loads (or even more frequently)?


Reproducible: Always

Steps to Reproduce:
1.prepare a cfg file (modify all.js to point to the config file), that points 
to a webserver location with the js script file (that modifies the proxy and 
homepage settings).
2. launch firefox and close firefox.  look at the pref.js file in user profile.
3. change the web server js file to point to another homepage or proxy.  
launch firefox and close firefox.  look at the pref.js file.

Actual Results:  
the file was not changes (and firefox used the old settings).

Expected Results:  
changed to the new proxy or new homepage.


Delete the failover.jsc and prefs.js (or proxy info in the pref) and it will 
reevaluate.

Comment 1

[Mike Connor [:mconnor]]

if you're not locking the prefs, you're only changing the defaults, and user
prefs will override changed defaults.

If you're locking the prefs, the prefs.js settings are overridden anyway, I
don't know whether we ignore or remove user prefs in that case, but that's
mostly academic anyway, since what matters is the actual behaviour, not whether
we retain user prefs that we ignore.

Comment 2

[ozzy osbourne]

I am using the lockpref but it is not enforced in the browser or the prefs.js 
file.  Is there another way to lock down the prefs?

Comment 3

[Mike Connor [:mconnor]]

pref locking works just fine (we have a lot of companies using it successfully
on the same platform, so we know its not broken).  The pref will show as locked
in about:config if you are doing it correctly.  If you are not, please look for
help via one of the support avenues that are available (this is a bug tracking
database, not a support forum).