[Webkit-unassigned] [Bug 265151] `WebAssembly` is no longer part of the global object

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Nov 22 17:34:12 PST 2023


https://bugs.webkit.org/show_bug.cgi?id=265151

--- Comment #17 from Justin Michaud <justin_michaud at apple.com> ---
>I can't use a `WKWebView` because I need my Wasm module import functions to be defined as JS callbacks

If you try https://developer.apple.com/documentation/webkit/wkscriptmessagehandler with worker + SAB + Async.await, you can probably get a nice speed improvement.

In particular, I have been meaning to hack up a demo of how to do this for a while. It is a recipe for a much more responsive user experience, but I understand it is a lot of glue code.

> I'm sorry but… before running into this project, we have tested running Wasm on iOS and it was working great via JSC

Do you have a test case that reproduces this? The current test case does not actually execute any wasm. As Mark said, this should have crashed the second you tried to actually use WASM, unless you were using a WKWebView. Simulator acts mostly like macOS, so it is super important to test on real hardware.

> Anyway, is there a chance that we will be able to run Wasm in a short-future without JIT, only purely with LLInt? Or is there a chance that JIT will be enabled inside JSC C API? Do you have a public roadmap about that topic?

We have nothing public at this time

> where I can't use another Wasm runtime
You totally can, you just can't use JIT. For example, this claims to support iOS: https://github.com/wasm3/wasm3 (I have never used this, this is not an endorsement).

We certainly do hope you try to use a WKWebView + callbacks though.

Above all, the key takeaway is this: 

***Opt out of hardened runtime on macOS to continue JITTIng. If that doesn't fix your problem, then this is a bug on our end that we need to fix. ***

If wasm was ever running on iOS outside of a WKWebView, that certainly surprises everyone on our end.

Cheers!

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20231123/0f48b24e/attachment.htm>


More information about the webkit-unassigned mailing list