Resolution has been reached. The behavior is as follows, and needs to be documented - BCD `'wasm-unsafe-eval'` entry at https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/content_security_policy - note on how/when WebAssembly (wasm) can be used, at https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/content_security_policy In Firefox: - Firefox 101 and earlier: extensions are unconditionally able to use wasm in extensions. - Firefox 102 (bug 1740263): * MV2 extensions can continue to use wasm in extensions by default, unless they have specified a custom content_security_policy that disallows `'wasm-unsafe-eval'`. * MV3 extensions cannot use wasm by default, but they can once they add `'wasm-unsafe-eval'` to `content_security_policy` in In Chrome: - Chrome 101: extensions not able to use wasm - Chrome 102: extensions unconditionally able to use wasm (bug) (same behavior as Firefox 101 and earlier) - Chrome 103: extensions can use wasm only if they add `'wasm-unsafe-eval'` to `content_security_policy` in manifest.json (https://crbug.com/1318922).
Bug 1766027 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Resolution has been reached. The behavior is as follows, and needs to be documented - BCD `'wasm-unsafe-eval'` entry at https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/content_security_policy - note on how/when WebAssembly (wasm) can be used, at https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/content_security_policy In Firefox: - Firefox 101 and earlier: extensions are unconditionally able to use wasm in extensions. - Firefox 102 (bug 1740263): * MV2 extensions can continue to use wasm in extensions by default, unless they have specified a custom content_security_policy that disallows `'wasm-unsafe-eval'`. * EDIT: given regressions, this has changed to: M2 extensions can unconditionally use wasm (see bug 1770909). * MV3 extensions cannot use wasm by default, but they can once they add `'wasm-unsafe-eval'` to `content_security_policy` in In Chrome: - Chrome 101: extensions not able to use wasm - Chrome 102: extensions unconditionally able to use wasm (bug) (same behavior as Firefox 101 and earlier) - Chrome 103: extensions can use wasm only if they add `'wasm-unsafe-eval'` to `content_security_policy` in manifest.json (https://crbug.com/1318922).