Player initialization stalls when fetch for wasm file fails

[nickfujita]

There is a missing case in the emscripten module fails to fetch the wasm file. Once the following PR is merged and released, we can update the emscripten version to resolve this:
emscripten-core/emscripten#13516

[TheOneric]

@nickfujita Can you elaborate on what you think should happen and why?
Perhaps I'm missing something, but it seems to me there just isn't much that can be done if fetching the wasm-binary fails; it is crucial for the the functionality. There is no way to operate without successfully loading (one of the two) "binaries". If fetching fails, JSO must abort.
In theory it would be possible to retry with the non-wasm-"binary", but at first glance this doesn't appear to me as being really helpful: Either there's a problem with the network and fetching the other "binary" will (very likely) fail as well, or the server is misconfigured and only allows fetching/hosts the non-wasm-binary, in which case this would only mask a server-side error.

[TheOneric]

Closing due to inactivity by OP. Can be reopened if OP responds with an explanation of the suggestion.