In chrome, wasm isn't enabled by default even on canary; you can enable it from chrome://flags
On Fri, Nov 4, 2016, 10:33 AM Alon Zakai <[email protected]> wrote: > Is that on latest Chrome Canary? > > On Thu, Nov 3, 2016 at 5:47 PM, Mark Sibly <[email protected]> wrote: > > ...the only slight bummer is it's only working in nightly. In chrome I get > this in the .js file... > > Uncaught TypeError: Right-hand side of 'instanceof' is not an object(…) > > ...here (line 202)... > > if (!(Module['wasmMemory'] instanceof WebAssembly.Memory)) { > > I *did* strip out the asm.js and .wast files before uploading but I'm > guessing that's not it. > > On Wednesday, November 2, 2016 at 3:41:16 PM UTC+13, Mark Sibly wrote: > > Hi, > > Ok, got my first wasm app built, but when I tried to visit it via browser > I get: > > Assertion failed: on the web, we need the wasm binary to be preloaded and > set on Module['wasmBinary']. emcc.py will do that for you when generating > HTML (but not JS) > > Does this mean I need to --preload-file the output file with the .wasm > extension when linking? > > This I can do, but I'm not sure what 'set on Module['wasmBinary]' involves. > > Bye! > Mark > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
