-
Notifications
You must be signed in to change notification settings - Fork 119
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 violation #94
Comments
This is definitely valid, but I'm not sure what the best way to solve this is.
In my experience, the CSP plugin doesn't produce a ton of valuable, actionable information as is, so I don't know that this is a very important issue to fix. |
Given that you want it on the tag of the ember component, could you not just add "display" to the list of attributeBindings and then add a display property to the component? CSP is actually pretty darn useful and this issue prevents this very popular addon from being using in anything other than a CSP reporting mode. Plus the ember-cli-content-security-policy addon has been getting some love lately in order to make it more usable/useful. |
To fix the CSP error described in iStefo#94.
I'm definitely open to trying to fix it, it just wasn't clear to me how to do it after thinking about how to do it for about 10 minutes.
If I were to add
and I think the best bet is to make use of |
This component generates a CSP violation using the default ember-cli CSP settings; you need to add a
'style-src': 'unsafe-inline'
directive to your server to make it go away.It looks like the style binding is never updated after component creation, so it could easily be replaced with a CSS class thereby eliminating the CSP violation.
The text was updated successfully, but these errors were encountered: