search

MobileChromeApps / mobile-chrome-apps

Chrome apps on Android and iOS
BSD 3-Clause "New" or "Revised" License
2.5k stars 347 forks source link

Latest update v0.6.0 breaks project (Content-Security-Policy) using Polymer #544

Closed bungoboingo closed 9 years ago

bungoboingo commented 9 years ago

I need to use inline scripts with Google Polymer and it appears that the new update has made it so that Content-Security-Policy is enabled by default. The documentation says this:

"Content-Security-Policy now works and enabled by default (can be disabled though)"

How do I disable it? I can't find it listed anywhere. Thanks.

sLatzko commented 9 years ago

Mine does work with cca 0.6.0.

Do you use vulcanize, so you don't violate the csp? https://www.polymer-project.org/0.5/articles/concatenating-web-components.html

ragingwind commented 9 years ago

If would you like to use vulcanize(with gulp) on developing with cca. Take look this: https://github.com/ragingwind/mobile-chrome-apps-starter-kit

bungoboingo commented 9 years ago

I'll give Vulcanize a try, thanks.

agrieve commented 9 years ago

So you know - The CSP values options are documented here: https://github.com/MobileChromeApps/mobile-chrome-apps/blob/master/docs/NextSteps.md

so, you'd use "cspUnsafeEval":"true" in your manifest.mobile.json