wasm with Manifest v3

[Cameron Taggart]

I wrote my Chrome extension primarily using Rust compiled to WebAssembly. How do I allow the wasm module to be loaded using the Manifest v3 format? With Manifest v2, I have this:

  "content_security_policy": "script-src 'self' 'wasm-eval'; object-src 'self'",

With Manifest v3, I get an error with this:

  "content_security_policy": {

    "extension_pages": "script-src 'self' 'wasm-eval'; object-src 'self'"

  },

Error

'content_security_policy.extension_pages': Insecure CSP value "'wasm-eval'" in directive 'script-src'.

Could not load manifest.

Without wasm-eval, I get this error:

Uncaught (in promise) CompileError: WebAssembly.instantiateStreaming(): Wasm code generation disallowed by embedder

What can I do to load wasm modules using the Manifest v3 format?

[Deco]

As per the Manifest V3 documentation, it is not directly possible to load WASM files with V3.

See the MV3 migration guide for instructions on how to implement remote configurations.

Thanks,

Deco

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/CAABik%3DupZxNqAwzWvLOjK552%3D_jryE9wYwBSJvRwdM%2BQjuabtw%40mail.gmail.com.

[Cameron Taggart]

The wasm module is not remotely hosted.

[Jackie Han]

The key problem is that the browser disallows various 'eval' in Manifest v3.

You could follow Wasm's progress on this issue

https://github.com/WebAssembly/content-security-policy/issues/7

https://github.com/WebAssembly/content-security-policy/blob/master/proposals/CSP.md

PS: I am not very familiar with wasm, but the problem should be this.

--

You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/CAABik%3DupZxNqAwzWvLOjK552%3D_jryE9wYwBSJvRwdM%2BQjuabtw%40mail.gmail.com.

--

Jackie Han

[wOxxOm]

There's https://crbug.com/948834 but I think you should open a new issue on https://crbug.com/  specifically about ManifestV3 because it's pretty likely Chromium developers are unaware they broke this feature.

[Maksim Ivanov]

Hello,

Did you try passing the DYNAMIC_EXECUTION=0 flag to Emscripten?

See https://github.com/emscripten-core/emscripten/blob/f825fa99d9605437c0fae0abada4e9113b36c833/src/settings.js#L1044 .

Maksim

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/e2bc2dba-45f0-4d68-8c82-e26bc7bb192cn%40chromium.org.

[Simeon Vincent]

+1 to the bug report request. More specially, please file a bug for adding Wasm support to MV3. This may be caused by a technical limitation of what's possible in in Chrome rather than a MV3 specific oversight, but regardless having an issue to specifically track this use case will help us chase it down.

Cheers,

Simeon - @dotproto

Chrome Extensions DevRel

[Cameron Taggart]

OK. Created https://crbug.com/1173354.

[ULViDO]

thank you for opening this post. I have the exact same issue. I have a local .wasm file crated with rust but can't be able to run in mv3. any luck?