dotnet.create() does not throw error when WebAssembly.instantiateStreaming() fails

[FranklinWhale]

Description

When WebAssembly fails to instantiate, the hosting webpage should be able to display an error to the user. Currently, dotnet.create() just fails with Uncaught (in promise) CompileError: WebAssembly.instantiateStreaming(), even when it is inside a try ... catch block.

Reproduction Steps

1. Build a .NET WASM Browser project that uses SIMD
2. Put dotnet.create() in try and console.log a message in catch
3. Open the webpage using Microsoft Edge with Enhanced Security Mode

Expected behavior

The message should be logged in console

Actual behavior

Uncaught (in promise) CompileError: WebAssembly.instantiateStreaming()

Regression?

No response

Known Workarounds

No response

Configuration

.NET 7 RC2
Microsoft Edge Version 107.0.1418.26 (Official build) (64-bit)

Other information

No response

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Description

When WebAssembly fails to instantiate, the hosting webpage should be able to display an error to the user. Currently, dotnet.create() just fails with Uncaught (in promise) CompileError: WebAssembly.instantiateStreaming(), even when it is inside a try ... catch block.

Reproduction Steps

1. Build a .NET WASM Browser project that uses SIMD
2. Put dotnet.create() in try and console.log a message in catch
3. Open the webpage using Microsoft Edge with Enhanced Security Mode

Expected behavior

The message should be logged in console

Actual behavior

Uncaught (in promise) CompileError: WebAssembly.instantiateStreaming()

Regression?

No response

Known Workarounds

No response

Configuration

.NET 7 RC2
Microsoft Edge Version 107.0.1418.26 (Official build) (64-bit)

Other information

No response

Author:	FranklinWhale
Assignees:	-
Labels:	arch-wasm, untriaged
Milestone:	-

[marek-safar]

/cc @pavelsavara @kg

[FranklinWhale]

Will the fix be backported to 7.0.x?