Open
Bug 521891
Opened 15 years ago
Updated 13 years ago
Need pref pane entry for extension blocklist feature
Categories
(SeaMonkey :: Preferences, defect)
SeaMonkey
Preferences
Tracking
(seamonkey2.1 wontfix)
NEW
Tracking | Status | |
---|---|---|
seamonkey2.1 | --- | wontfix |
People
(Reporter: mnyromyr, Unassigned)
References
()
Details
Attachments
(1 file)
3.76 KB,
patch
|
Details | Diff | Splinter Review |
All our privacy-relevant features (as stated in the current draft for the SeaMonkey Privacy Policy, see URL) are configurable in the preferences, except for the extensions blocklist feature. While, in toto, it's very desirable to have it enabled always, it is indeed a privacy violation and sensitive users should have the possibility to configure this without resorting to hacking about:config. In fact, "hiding" this there would be rather misleading and, well, dishonest. The attached patch is proposal as a discussion base for including this for the SeaMonkey 2.1 timeframe. It places the pref entry onto the software installation pane, with rather negative wording. Comments?
Comment 1•15 years ago
|
||
The wording should make clear that turning this off enables add-ons and plugins that are known to be harmful, but I think this already comes near to what it should be. As it introduces a new string, it of course can go into 2.1 only right now.
Is it possible (by design of the blocklist system) that the blocklist remains enabled but specific plug-ins receive an "override" by the user?
Reporter | ||
Updated•15 years ago
|
Flags: wanted-seamonkey2.1? → wanted-seamonkey2.1+
Updated•15 years ago
|
Status: NEW → ASSIGNED
Updated•14 years ago
|
status-seamonkey2.1:
--- → wanted
Flags: wanted-seamonkey2.1+
Comment 4•13 years ago
|
||
Karsten's not working on this, has l10n impact, won't land in 2.1
Assignee: mnyromyr → nobody
Target Milestone: seamonkey2.1a1 → ---
Updated•13 years ago
|
Status: ASSIGNED → NEW
You need to log in
before you can comment on or make changes to this bug.
Description
•