Issue regarding chrome's csp
See original GitHub issue@cburgmer first of all a really nice project!
Now to the problem:
I’m trying to use it in an atom package but due to their csp policy I can’t seem to generate an image.
I’m getting this error:
Refused to load the image 'blob:file%3A///0daa8856-e790-486e-9de1-d1c5a3978ae3' because it violates the following Content Security Policy directive: "img-src data: *".
I see that it is because of blobs being blocked by their csp,
is their any way we can do it with data urls?
Any solutions/suggestions?
Thanks you 😃
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Implementing CSP and Trusted Types debugging in Chrome ...
This blog post is about the implementation of DevTools support for debugging Content Security Policy (CSP) issues with the help of the ...
Read more >CSP error noise caused by Chrome extensions - DebugBear
Chrome extensions can sometimes generate unnecessary Content Security Policy reports. This article looks at what causes these noisy alerts.
Read more >blocked:csp Understanding why CSP blocks resources
You may be seeing blocked:csp in Chrome developer tools when the browser ... CSP stands for Content Security Policy, and it is a...
Read more >How to relax Content Security Policy in Chrome? - Super User
You will need to use sandboxing to isolate any content that you want to do 'eval' things to. Sandboxing lifts CSP on the...
Read more >Disable Content-Security-Policy
Click the extension icon to disable Content-Security-Policy header for the tab. Click the extension icon again to re-enable Content-Security- ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes the issue seems to be resolved for now. Although I havent had the time to test it on the latest version of Atom. It is safe to assume that it should work here as well. Closing the issue now, will reopen in case of a problem.
Just out of interest, did you manage to fix the problem?
If so, we should keep this issue open so we can provide a proper workaround.