-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Library is blocked when CSP header 'unsafe-eval' is not specified #1274
Labels
Comments
I'm working on complete rewrite it's almost ready. But e2e and unit test are not with 100% coverage yet. I think it would be published this weekend. |
@all-contributors please add @mpschaeuble for bug |
I've put up a pull request to add @mpschaeuble! 🎉 |
Should be fixed in v15.0.0 |
Thanks, works perfectly now! |
@mschaeuble nice to hear that |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When 'unsafe-eval' is not specified in the Content-Security-Policy header, the execution of ng-in-viewport is blocked by the browser. The issue occurs at least in Version 13.0.1.
This seems to be a regression bug: #333
The text was updated successfully, but these errors were encountered: