Comment on attachment 8613433 Allow .js preference files to set locked prefs with lockPref()
Because this came up on the mailing list, I'll try to be explicit about the decision here. I don't think we should allow extensions to lock preferences, and we don't even have a clear description (other than this code) of what it means to "lock" a preference: whether changes to the default value are still allowed, or the user value, etc. The code is the incidental part of this; it's the basic problem and solution space that's totally unclear. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/541951 Title: Firefox 3.6 does not honour lockPref Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Binary package hint: firefox In firefox 3.5 the following worked: Set lockPref("network.proxy.type", 5); in /etc/firefox-3.5/pref/firefox.js Setting lockPref in /etc/firefox/pref/firefox.js in firefox 3.6 does not lock down the proxy. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/541951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
