Bug 1915254 Comment 1 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I think this is because the exception's `tag` (from `WasmExceptionObject::wrapJSValue`) is the `WebAssembly.JSTag` object from the realm where we throw.

If I change the test to use `tag: s3.WebAssembly.JSTag` instead of `tag: WebAssembly.JSTag` the exception is caught.

I don't know what the spec says about JS exception wrapping and in which realm this should happen.
Revision 1 by
on 
I think this is because the exception's `tag` (from `WasmExceptionObject::wrapJSValue`) is the `WebAssembly.JSTag` object from the realm we're in when we enter `wasm::HandleExceptionWasm`.

If I change the test to use `tag: s3.WebAssembly.JSTag` instead of `tag: WebAssembly.JSTag` the exception is caught.

I don't know what the spec says about JS exception wrapping and in which realm this should happen.

Back to Bug 1915254 Comment 1