141772 - [RFE] Separate pref files for system-wide vis-a-vis user prefs.

Status: VERIFIED INVALID

(Core :: Preferences: Backend, enhancement)

Description

[Cyrus Patel]

When deploying Moz for a (large-)number of users/workstations, its possible to
give users a basic "template" prefs.js. However, when something system-wide
changes, the only way to get Moz to notice this change is to push a new prefs.js
 onto the users which implies that user personal settings get lost.

Might it be possible to have Mozilla look for "pre-" and "post-" prefs files
when loading prefs? 

The 'pre-' prefs file would contain default settings, but are overridable 
           by the user's own prefs.js (if the user decides to change them)
           In other words, these would be defaults that supercede 
           Moz's built-in defaults.
The 'post-' prefs file would contain settings that overrule prefs.js,
           proxy settings for example.
           It would be nice if the postload options were treated as 
           'read-only' in the sense that they wouldn't be present in the 
           preferences dialog, but this is not strictly necessary (only 
           wishful thinking).

Perhaps these two files could be automatically searched for in some 
subdirectory under the Mozilla installation (mozilla.org/default_prefs/ 
for example).

Comment 1

[Boris Zbarsky [:bzbarsky]]

The "pre-" files already exist -- all.js (loaded on all platforms), unix.js,
macprefs.js, etc

Confirming rfe to add the "post-" files.

Comment 2

[Brian Nesse (gone)]

The post- also exists in the form(s) of
 user.js - user editable prefs which override prefs.js
 netscape.cfg - Non editable preferences set with the CCK tool which override
                everything.

Not really INVALID, bug ALREADY_IMPLEMENTED isn't a resolution. :)

Comment 3

[Cyrus Patel]

In which directory can I put the all.js, user.js and netscape.cfg ? 
Do all these follow the user_pref("foo",1) method for setting options?

Comment 4

[Cyrus Patel]

er, never mind. I've figured out how all.js and user.js work. Thanks.

Comment 5

[sairuh (rarely reading bugmail)]

mass-verification of Invalid bugs.

if you don't think the report is invalid, please check to see if it has already
been reported (it might be a duplicate instead). otherwise, make sure that there
are steps (a valid test case) that clearly display the issue as an unexpected
defect.

mail filter string for bugspam: SequoiadendronGiganteum

Comment 6

[Brant Gurganus]

[RFE] is deprecated in favor of severity: enhancement.  They have the same meaning.