Closed
Bug 1581611
Opened 2 years ago
Closed 2 years ago
Support the content_scripts value in the content_security_policy dictionary
Categories
(WebExtensions :: General, enhancement, P2)
WebExtensions
General
Tracking
(firefox72 fixed)
RESOLVED
FIXED
mozilla72
| Tracking | Status | |
|---|---|---|
| firefox72 | --- | fixed |
People
(Reporter: mixedpuppy, Assigned: mixedpuppy)
References
(Blocks 2 open bugs)
Details
Attachments
(2 files)
The "content_scripts" allows extensions to define a default csp for content scripts.
| Assignee | ||
Comment 1•2 years ago
|
||
This WIP patch adds support for including content_scripts CSP in the extensions
manifest, along with all interfaces necessary to access the CSP value. This does not
implement actual use of the CSP for content scripts.
| Assignee | ||
Updated•2 years ago
|
Priority: -- → P2
| Assignee | ||
Comment 2•2 years ago
|
||
| Assignee | ||
Comment 3•2 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=0ebcb52528fa96b5f37fd6485c237688407bfbf0
| Assignee | ||
Comment 4•2 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=fe275de6b514d38ef140e2ed1aaf04b9e9d09c2d
Pushed by scaraveo@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a56f917583a6 Part 1: add content_scripts to the extension content_security_policy r=rpl,bzbarsky https://hg.mozilla.org/integration/autoland/rev/53390b20df64 Part 2: apply content script csp r=robwu,ckerschb
Comment 6•2 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/a56f917583a6
https://hg.mozilla.org/mozilla-central/rev/53390b20df64
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox72:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla72
Assignee: nobody → mixedpuppy
Comment 7•2 years ago
|
||
Hello,
Will this fix require manual validation? If yes, please provide some steps to reproduce in order to correctly test it and also, please set the "qe-verify+" flag. Otherwise, could the "qe-verify-" flag be added? Thanks!
Flags: needinfo?(mixedpuppy)
You need to log in
before you can comment on or make changes to this bug.
Description
•