From eb235404bdb1267dd3abd17a47a33312f51723dc Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Fri, 18 Aug 2023 10:01:08 -0400 Subject: [PATCH] Use 'wasm-unsafe-eval' instead of deprecated 'wasm-eval' Reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_webassembly_execution --- platform/common/vapi-background.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/platform/common/vapi-background.js b/platform/common/vapi-background.js index f0cbcdbb7..297e69b2b 100644 --- a/platform/common/vapi-background.js +++ b/platform/common/vapi-background.js @@ -42,7 +42,7 @@ vAPI.cantWebsocket = vAPI.canWASM = vAPI.webextFlavor.soup.has('chromium') === false; if ( vAPI.canWASM === false ) { const csp = manifest.content_security_policy; - vAPI.canWASM = csp !== undefined && csp.indexOf("'unsafe-eval'") !== -1; + vAPI.canWASM = csp !== undefined && csp.indexOf("'wasm-unsafe-eval'") !== -1; } vAPI.supportsUserStylesheets = vAPI.webextFlavor.soup.has('user_stylesheet');