Opened 22 months ago

Closed 22 months ago

Last modified 20 months ago

#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@… Blocked By:
Blocking: Platform: Unknown / Cross platform
Ready: yes Confidential: no
Tester: Ross Verified working: yes
Review URL(s):

https://codereview.adblockplus.org/29496582/

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.

Change History (7)

comment:1 Changed 22 months ago by kzar

  • Description modified (diff)
  • Priority changed from Unknown to P4
  • Ready set

comment:2 Changed 22 months ago by tlucas

  • Review URL(s) modified (diff)

comment:3 Changed 22 months ago by tlucas

  • Description modified (diff)
  • Resolution set to fixed
  • Status changed from new to closed

comment:4 Changed 22 months ago by kzar

  • Resolution fixed deleted
  • Status changed from closed to reopened

comment:5 Changed 22 months ago by abpbot

comment:6 Changed 22 months ago by kzar

  • Resolution set to fixed
  • Status changed from reopened to closed

comment:7 Changed 20 months ago 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.