Closed Bug 86932 Opened 23 years ago Closed 23 years ago

Fix per-site JS disabling

Categories

(Core :: Security: CAPS, defect, P1)

Product:
Core
Component:
Security: CAPS
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED FIXED
Milestone:
mozilla0.9.4

People

(Reporter: security-bugs, Assigned: security-bugs)

References

Details

(Whiteboard: patch)

Attachments

(1 file)

Patch to add this functionality
4.39 KB, patch
Details | Diff | Splinter Review
Completely disabling JS on a per-site basis was tossed out with the XPCDOM landing. We need to restore this feature.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.3
Priority: -- → P4
Blocks: 89297
*** Bug 89297 has been marked as a duplicate of this bug. ***
Does this bug cover the front end or the back end code?
This bug is about fixing the back-end for per-site javascript disabling. I don't think we've ever had a front-end for this feature, but see bug 38966 for making one. Bug 91779, "about:plugins does not work if javascript is disabled", may depend on this bug.
Target is now 0.9.4, Priority P1.
Priority: P4 → P1
Target Milestone: mozilla0.9.3 → mozilla0.9.4
r=jesse, sr=dougt
Whiteboard: patch
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Verified on 2001-09-20-Branch on WinNT 1. Did about:plugins (List of plugins are loaded). 2. Disabled javascript using Preferences 3. Did about:plugins (Nothing is loaded).
Status: RESOLVED → VERIFIED
*** Bug 107284 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: