Under Edit -> Preferences -> Appearance -> Themes Category the lockPref function for the pref lockPref("general.skins.selectedSkin", "modern/1.0"); /* apply modern */ or lockPref("general.skins.selectedSkin", "classic/1.0"); /* apply classic */ Doesn't visually lock down the panel. The pref is locked in the backend on browser restart the skin is not changed. The Apply Modern or Apply Classic is enabled and gives the user the impression that the skin is changeable. The pref "general.skins.selectedSkin" when locked should grey out the Apply button as well as grey out the Installed Themes Panel (to give user no option to change anything).

my bug..QA over to me.

The preference, |general.skins.selectedSkin|, is deleted from the pref system on browser startup and written out on exit. IOW, the pref does not exist while the pref dialog is up. This makes it impossible for me to check if this preference is locked, because it doesn't exist. So that leaves the following options: 1. rewrite the profile and theme code to work differently. 2. create a new pref to lock the ui, which requires the un-intuitive process of locking both the skin pref and the button for the pref ui. yuck. 3. mark this won't fix :)

->ben for triage

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420