Closed
Bug 1778975
Opened 2 years ago
Closed 2 years ago
nsCSPContext::LogViolationDetails has a lot of unused code
Categories
(Core :: DOM: Security, task)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
108 Branch
| Tracking | Status | |
|---|---|---|
| firefox108 | --- | fixed |
People
(Reporter: tschuster, Assigned: tschuster)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-backlog1])
Attachments
(1 file)
It seems like nsCSPContext::LogViolationDetails is mostly used for eval and wasm-eval nowadays. We can probably simplify this.
|
||
Updated•2 years ago
|
Severity: -- → N/A
Whiteboard: [domsecurity-backlog1]
|
Assignee | |
Comment 1•2 years ago
|
||
This also makes it obvious that we are using the correct effectiveDirective.
|
||
Updated•2 years ago
|
Assignee: nobody → tschuster
Status: NEW → ASSIGNED
Pushed by tschuster@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1823bb3c0137 Specialize nsCSPContext::LogViolationDetails for (wasm) eval. r=freddyb
|
||
Comment 3•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox108:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 108 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•