Closed Bug 1258295 Opened 8 years ago Closed 8 years ago

Remove remnants of Security Policies preferences pane

Categories

(SeaMonkey :: Preferences, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
seamonkey2.45

People

(Reporter: nONoNonO, Assigned: rsx11m.pub)

References

()

Details

Attachments

(1 file, 1 obsolete file)

While checking the Dutch translation of SeaMonkey, I stumbled upon the file suite/chrome/common/pref/pref-policies.dtd which strings I couldn't find in the UI. Investigating a bit I noticed the Security Policies pane was commented out in bug 44121, because it was broken.

Please fix the Security Policies pane or strip it out completely.
Summary: Restore or remove Policies preferences pane → Restore or remove Security Policies preferences pane
Given bug 38966 comment #176 and bug 38966 comment #177, it appears that whatever this pane was supposed to cover has been covered by CAPS, which in the end got removed by bug 913734, and is now (not as security "zones" but by individual domain permissions) covered by the Data Manager coming directly with SeaMonkey. Thus, I'm voting for removal of the remaining XUL/DTD code (I couldn't find any related JavaScript snippets).
Attached patch Remove dead code (obsolete) — Splinter Review
Patch based on search results. The string "Security Policies" didn't show any hits for the Help content, thus apparently was removed from there already.
Blocks: BlockJS
Missed a string.
Assignee: nobody → rsx11m.pub
Attachment #8734237 - Attachment is obsolete: true
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Attachment #8734339 - Flags: review?(iann_bugzilla)
Blocks: 1259422
Attachment #8734339 - Flags: review?(iann_bugzilla) → review+
Summary: Restore or remove Security Policies preferences pane → Remove remnants of Security Policies preferences pane
Pushed to trunk, http://hg.mozilla.org/comm-central/rev/9d94f84acb2e
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.45
You need to log in before you can comment on or make changes to this bug.