I wanted to experiment with Javascript and created a file that I opened in Firefox (68.0.1) file:///C:/play/my.html
. The file is on JSFiddle at https://jsfiddle.net/PatS2265/7r4j6ewa/ (but the code works in JSFiddle).
In Firefox when I opened this file I got the following error in the console:
Content Security Policy: The page's settings blocked the loading of a resource at inline (“script-src”).
I looked up how to fix this and tried adding:
<meta http-equiv="Content-Security-Policy" content="default-src *; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' 'unsafe-eval' http://www.google.com">
but this didn't fix it. The file is shown below (with my failed attempt at adding the Content-Security-Policy meta tag.
What is the correct syntax for the Content-Security-Policy?
NOTE: In Chrome (v76.0.3809.100), this file just worked so that my work around for now.
<!DOCTYPE html>
<html>
<head>
<title>My Async Test</title>
<meta http-equiv="Content-Security-Policy" content="default-src *; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' 'unsafe-eval' http://www.google.com">
<meta charset="UTF-8" />
</head>
<body>
<script>
function clickMe() {
f().then(alert);
}
async function f() {
return 1;
}
</script>
Just testing
<button type="button" onclick="clickMe()">Run Async Function</button>
</body>
</html>
Searches
I did a search for how to fix this and came across a solution to disable the Content-Security-Policy.
Other results that were helpful were:
I just found tag in StackOverflow for content-security-policy so I'll start that search now.
Well I feel a little bit embarrassed that I didn't get this sooner. I have to credit @Nickolay for commenting that he did not see this problem and asked if it could be an AddOn, or if I had tried this in a new profile, so I checked both.
I created a clean profile using about:profiles
and clicking on Create a New Profile
, and when I ran in that profile it worked!
Next I realized that I had the Add-On NoScript enabled which was preventing Javascript from running on the on the local files ( file:///C:/
)!
After I enabled local files in NoScript the problem went away.
Doh (hand hitting forehead).
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.