Does that happen even on a simple hello world program using wasm? Or is this a special case somehow?
On Mon, Feb 5, 2018 at 1:07 PM, Charles Vaughn <[email protected]> wrote: > Getting this error in Chrome 64 and Chrome Canary: > > The source list for Content Security Policy directive 'default-src' > contains an invalid source: ''wasm-eval''. It will be ignored. > runtimeweb.pretty.js:1063 [Report Only] Refused to compile or instantiate > WebAssembly module because 'wasm-eval' is not an allowed source of script > in the following Content Security Policy directive: "script-src *". > > doNativeWasm @ runtimeweb.pretty.js:1063 > Module.asm @ runtimeweb.pretty.js:1134 > (anonymous) @ runtimeweb.pretty.js:6121 > > I've tried enabling the 'wasm-eval' source option, but it seems Chrome > only supports that for extensions. I do not get CSP errors in Firefox or > Edge. > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
