Opened on 07/24/2017 at 11:08:08 AM
Closed on 07/25/2017 at 10:48:13 AM
Last modified on 09/18/2017 at 01:32:11 PM
#5448 closed change (fixed)
Add content_security_policy to the manifest.json for Chrome-extensions
| Reported by: | tlucas | Assignee: | |
|---|---|---|---|
| Priority: | P4 | Milestone: | |
| Module: | Automation | Keywords: | |
| Cc: | kzar, snoack, brent@getadblock.com | Blocked By: | |
| Blocking: | Platform: | Unknown / Cross platform | |
| Ready: | yes | Confidential: | no |
| Tester: | Ross | Verified working: | yes |
| Review URL(s): | |||
Description (last modified by tlucas)
Background
Google Chrome allows the usage of a custom content security policy, which can be included in an extension's manifest.json using the content_security_policy option.
What to change
Make the buildtools include the content_security_policy option
"content_security_policy": "<policy>"
when building the Chrome extension if the "contentSecurityPolicy" metadata option is specified.
Attachments (0)
Change History (7)
comment:1 Changed on 07/24/2017 at 11:41:53 AM by kzar
- Description modified (diff)
- Priority changed from Unknown to P4
- Ready set
comment:3 Changed on 07/24/2017 at 02:24:04 PM by tlucas
- Description modified (diff)
- Resolution set to fixed
- Status changed from new to closed
comment:4 Changed on 07/24/2017 at 02:36:12 PM by kzar
- Resolution fixed deleted
- Status changed from closed to reopened
comment:5 Changed on 07/25/2017 at 10:45:32 AM by abpbot
comment:6 Changed on 07/25/2017 at 10:48:13 AM by kzar
- Resolution set to fixed
- Status changed from reopened to closed
comment:7 Changed on 09/18/2017 at 01:32:11 PM by Ross
- Tester changed from Unknown to Ross
- Verified working set
Done. Content security policy string is included in manifest if present in metadata.
adblockpluschrome / 1846:44197859df84
Note: See
TracTickets for help on using
tickets.
A commit referencing this issue has landed:
Issue 5448 - Add content_security_policy to manifest.json if available