265557 - Preferences -->Privacy & Security -->Master Password --> "Master Password Timeout" is not lockable

Status: RESOLVED INVALID

(SeaMonkey :: Preferences, defect)

Description

[Boying Lu]

1. create a file named mozilla.cfg under dist/bin directory. it contains
following two lines:
   //silly comment
   lockPref("security.ask_for_password",1);

2. modifiy the dist/bin/greprefs/all.js as following:
   remove the line: 
   pref("general.config.obscure_value", 13); // for MCD .cfg files
   add the following two lines:
   pref("general.config.filename","mozilla.cfg");
   pref("general.config.obscure_value", 0); 

3. launch mozilla
4. select Edit->Perferences... menu item
   a window will popup
5. select Privacy&Security-->Master Passwords

actual results:
Master Passwords timeout field "The firsttime it is needed" is selected

expectual results:
"Every time it is needed" should be selected.

Comment 1

[Boying Lu]

Attachment: patch v0

Comment 2

[Boying Lu]

The value should selected should be based on prefstring.

Comment 3

[Boying Lu]

Comment on attachment 162962 [details] [diff] [review]
patch v0

can you give r? Thanks

Comment 4

[[e-mail]]

Comment on attachment 162962 [details] [diff] [review]
patch v0

The prefstring is not actually used within Mozilla. The value is instead saved
to secmod.db and I don't know if it should be lockable.

Comment 5

[Boying Lu]

I think the logical is unreasonable in onMasterPasswordLoad().  I think for
every xul element,it gets(or sets) its value based on "prefstring" attribute.
This provides user a unified method to control all these UI elements.

For the first time, "prefstring" is not sync with the element's value, But after
changing the setting by user, "prefstring" is synced with the value. Since these
two values should is synced afterward, why they are not synced from the beginning?

Comment 6

[Serge Gautherie (:sgautherie)]

(Filter "spam" on 'prefs-nobody-20080612'.)

Comment 7

[Ian Neal]

The pref security.ask_for_password is no longer used.
->INVALID