-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--csp option doesn't work with noscript #1663
Comments
I faced the exact same issue. |
I may hit the same problem.
It does not point the right error place, as
This case, console shows that the error happens at My Apps imports core-toolbar that vkammerer said it used noscript. Do you know any workaround for this? |
Refer to @robdodson comment on Polymer/polymer#613 (comment) |
Thanks, I'll track related issues. FYI, I modified core-toolbar to have a dummy script and removed noscript attribute. It works for me as a quick workaround. |
Thanks @toyoshim ! I was facing the same issue and adding the dummy script with removing the noscript attr solved it for me too. |
Fixed by Polymer/polymer-bundler@e068dee. Using |
👍 |
Packages that include a "noscript" attribute (like the "core-toolbar" and "core-field" packages) make vulcanize generate an inline "script" tag, even when the --csp option is used. This triggers errors when used in a chrome packaged app (and is obviously a bug since the point of --csp is to get rid of inline scripts).
I don't know if this should be fixed in the packages themselves or in vulcanize, so I just open this issue here.
The text was updated successfully, but these errors were encountered: