If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

CFG Activation broken on latest trunk builds

VERIFIED FIXED in mozilla0.9.8



Preferences: Backend
16 years ago
16 years ago


(Reporter: Rodney Velasco, Assigned: Brian Nesse (gone))



Firefox Tracking Flags

(Not tracked)



(2 attachments)



16 years ago
Customized CFG will not load if activated in the all.js file.  Problem started
on the December 21, 2001 night builds.  Critical bug that affects AutoConfig and
preference locking.

Steps to Reproduce:
1. Download attached mozilla.cfg file to computer, download and name the file to

*hashed file that contains the following preferences*
lockPref("general.startup.browser", true ); /* Navigator */
lockPref("general.startup.mail", true); /* Mail */

2. Place mozilla.cfg file in the program directory containing the mozilla
executable (for mac place in the Essential Files Folder)
3. Add these lines to your all.js file located in the bin\defaults\pref directory.

pref("general.config.filename", "mozilla.cfg");
pref("general.config.vendor", "mozilla");

4. save all.js file and start Mozilla

Expected Result:
Mozilla should startup with Both the browser and mail client.  
Open General Prefences panel choose the 'Appearance' Category, in the Mozilla
should start up field:

1) Navigator checkbox should be checked and greyed out.  User should not be able
to modify checkbox.
2) Mail checkbox should be checked and greyed out.  User should not be able to
modify checkbox.

Actual result:
Browser starts up mail doesn't.  Both fields in preference panels can be
modified by user even though I specified a lockPref() for both preferences.

Might be a regression of bug 89137.


16 years ago
QA Contact: sairuh → rvelasco

Comment 1

16 years ago
Created attachment 64077 [details]
CFG file containing lockPref() functions to start browser and mail client.

Comment 2

16 years ago
adding nsbeta1 keyword, very bad bug for us Customization Folks that require CFG
activation and AutoConfig for our testing.
Keywords: nsbeta1

Comment 3

16 years ago
Hi, Rodney:

Is this a QA blocker for us? My impression is that QA couldn't test
auto-config-ed features at all with the recen build?

Hi, Brian/Jud: any chance we treat this as a p0? Is there an ETA on this?


Comment 4

16 years ago
Created attachment 64192 [details] [diff] [review]
Proposed patch.

There are 2 problems here. First, the windows build system apparently changed
out from under the patch in bug 89137 while it was waiting to land. Second,
none of the autoconfig stuff was ever added to the installer packages so
autoconfig only works in a debug build.

Comment 5

16 years ago
I have also added the appropriate bits to the static build packages. The only 
thing I don't know for certain here is if the autoconfig module is built as part 
of the static build process.

Adding some folks I hope have some packaging knowledge to the cc list. Alec, JJ, 
Simon, can you guys r/sr these changes in attachment 64192 [details] [diff] [review] please?
Target Milestone: --- → mozilla0.9.8

Comment 6

16 years ago

Brian - thanks for the quick response.
QA - would you notify Yumi to deliver a build when the patches checked in.


Comment 7

16 years ago
Tao,yes this is a blocker for QA. No way to test autoconfig and pref locking of
new preferences added to the trunk.  

Comment 8

16 years ago
Comment on attachment 64192 [details] [diff] [review]
Proposed patch.

Attachment #64192 - Flags: superreview+

Comment 9

16 years ago
Comment on attachment 64192 [details] [diff] [review]
Proposed patch.

Attachment #64192 - Flags: review+

Comment 10

16 years ago
Fix checked in.
Last Resolved: 16 years ago
Resolution: --- → FIXED

Comment 11

16 years ago
Tested CFG activation on

Linux: 2002012208 trunk
Win2K: 2002012203 trunk
Mac OSX: 2002012208 trunk

Marking bug verified.
You need to log in before you can comment on or make changes to this bug.