CSP stopping 'eval' from working in Firefox
See original GitHub issueDescribe the bug JavaScript challenges currently cannot be completed in Firefox, reported here: https://www.freecodecamp.org/forum/t/evalerror-call-to-eval-blocked-by-csp/339919/6
To Reproduce Steps to reproduce the behavior:
- Go to any JavaScript challenge, e.g. https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures/basic-javascript/comment-your-javascript-code
- See
EvalError: call to eval() blocked by CSP
in the console
Desktop (please complete the following information):
- Browser Firefox
- Version 72.0.1 (64-bit)
Issue Analytics
- State:
- Created 4 years ago
- Comments:18 (18 by maintainers)
Top Results From Across the Web
Enabling CSP causes add-ons to receive rejection notices
If you have Adblock Ultimate (or AdGuard) enabled and open the script in Firefox with Web Console open (Ctrl+Shift+K), you will see the...
Read more >1645614 - CSP errors when "Using eval in content scripts"
Hi, Tampermonkey dev here. I start to sorely miss a Firefox feature more and more. Please install the attached example extension in Chrome...
Read more >CSP: script-src - HTTP - MDN Web Docs - Mozilla
If a page has a CSP header and 'wasm-unsafe-eval' isn't specified in the script-src directive, WebAssembly is blocked from loading and ...
Read more >The page's settings blocked the loading of a resource: xyz ...
This warning message means that due to the existence of a particular CSP directive, a resource wasn't loaded. See also. CSP errors and...
Read more >Content Security Policy - Mozilla - MDN Web Docs
Content Security Policy (CSP) is a mechanism to help prevent websites ... The extension is not allowed to evaluate strings as JavaScript.
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
We updated the CSP and this is resolved in our staging instance and should be resolved in our production instance soon (it may take a bit to cascade through the cache).
Please let us know after a few hours and close if resolved. Thanks.
Yes, it’s working on my end. @beaucarnes also tested it during the deployment and everything seems fixed now.
Thanks again for all your help with this. Think we can close this issue for now, but I’ll keep an eye on the forum and Twitter to see if people are still having issues.