307881 - Lock option in about:config only locks settings with the default value

Status: RESOLVED INVALID

(Firefox :: Settings UI, defect)

Description

[Gert-Paul van der Beek]

With the introduction of the new Prefdialog a new option in about:config was
introduced: Lock.
If we want to lock setting which is modified, the default value is always used.
This seems unlogical to me, because not for everyone the default value is the
best value to use.

Steps to reproduce:
1. Open about:config and search for a setting, e.g. xpinstall.enabled. Dubble
click this setting so that the value changes (in this case to false).
2. Click with the right mouse button on xpinstall.enabled and choose for 'Lock'

Expected result: The pref xpinstall.enabled is locked with value false.
Actual result: The pref xpinstall.enabled is locked with value true (the default
value)

Comment 1

[Hermann Schwab]

I don't see any value in locking via about:config, imho locking was done long ago to enforce some settings companywide, if you can remove the lock via about:config, that doesn't make sense.

Some more info:
http://www.alain.knaff.lu/howto/MozillaCustomization/locked.html
You get shown how to produce a mozilla.cfg file containing your locked prefs, how to encode it using http://www.alain.knaff.lu/~aknaff/howto/MozillaCustomization/cgi/byteshf.cgi
and how to where to put it.

Tons of info:
Mozilla Profile Migration & FAQ - Mobile Profiles 
http://forums.mozillazine.org/viewtopic.php?t=54104

Mozilla AutoConfig - Networking Mozilla Profiles for 2000 Users
http://www.int-evry.fr/mci/user/procacci/netscape/en/mozilla-autoconfig-en.html 

Comment 2

[Mike Kaply [:mkaply]]

The ability to lock/unlock prefs from about:config was removed.