282541 - user.js lockPref settings are ignored

Status: RESOLVED INVALID

(Thunderbird :: Account Manager, defect)

Description

[Gregg Berkholtz]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

When setting apparently any setting, for example
"lockPref("mail.server.server2.userName", "UID");" Thunderbird does not actually
lock the setting, but acts as-if the configuration did not exist (showing an
empty field in the UI).

Reproducible: Always

Steps to Reproduce:
1. Goto a profile's user.js file and replace user_pref... with lockPref...
2. Start Thunderbird


Actual Results:  
Settings are not locked or filled in

Expected Results:  
Settings should be locked, and the text box should be greyed out.

In rolling out thunderbird to any business or educational enviroment, it's
frequently necessary to protect less-knowledgable users from themselves. In
doing so, we reduce our support calls by reducing the possiblity that a user
will change a setting which shouldnt have been changed. The Mozilla suite has
the ability to lock these settings down, Tunderbird is now a better option, and
we need to be able to do the same here.

For our needs, the settings include:
 Server, and account details such as:
  mail.identity.id*.*_folder
  mail.server.server*.directory
  mail.server.server*.hostname
  mail.server.server*.name
  mail.smtpserver.smtp*.hostname
  mail.smtpserver.smtp*.auth_method
  mail.smtpserver.smtp*.username
 Various UI settings (I'll update the ticket once I identify the more major ones).

Comment 1

[Gregg Berkholtz]

Changing OS to all - as I just confirmed the same issue on Linux (Thunderbird
V1.0 20050116)

Comment 2

[Frank Wein [:mcsmurf]]

Reporter: You can't set lockPref in your user.js, see
http://www.int-evry.fr/mci/user/procacci/netscape/en/mozilla-autoconfig-en.html
how locking prefs works. Also probably (i'm not sure, the other bug isn't too
specific) you have to wait until Bug 225288 is fixed, i CCed you over there.