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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/541951 Title: Firefox 3.6 does not honour lockPref To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/541951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
