It works for me: Safari 16.5(18615.2.9.11.4)
I remember having more or less the same issue with iOS 16.3 IIRC. and it disappeared after I’ve updated it.
I just complete my investigation there, and I confirm @Cedric is perfectly right.
Safari 16.3 is buggy, and upgrading to 16.5 works like charm. I tested this successfully on MacBook PRO 2018, and and iPad 2.
This also means that my old iPhone SE has been brickified (because I can’t do this upgrade).
The very weird thing is that this bug occurs also in Chrome and Firefox on my iPhone, and I cannot explain that. Probably more related with the OS than with the apps!
Anyway, I stop here. Thank you very much.
No, it’s a bit for complex than that. Some code/instructions work with the slow wasm (just after wasm has been loaded) but do not with the fast compilation of the wasm.
So, it’s a matter of finding what breaks, what happens, find a replacement and release a new version. This is very time consuming and wihtout a guarantee that next version of Safari will fix it or will not add new bugs. The only valid solution to me is to put pressure on Apple to force them to respect standards and be more reliable.