Skip to content

[js-api] Expose Tag/Exception everywhere - #2260

Merged
Ms2ger merged 1 commit into
WebAssembly:mainfrom
kaist-plrg:fix/js-api-tag-exception-exposed-everywhere
Oct 2, 2026
Merged

Ms2ger merged 1 commit into
WebAssembly:mainfrom
kaist-plrg:fix/js-api-tag-exception-exposed-everywhere

Conversation

@f52985

@f52985 f52985 commented Oct 2, 2026

Copy link
Copy Markdown
Collaborator

#1550 exposed every interface in the WebAssembly namespace everywhere (Exposed=*), but Tag and Exception predate that PR by three years (added in 2019's exception-handling support; #1550 landed in 2022) and were never swept up in it.

This applies the same change to these two interfaces it missed.

(Although I'm not entirely sure about what this does, tbh)

@Ms2ger Ms2ger left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change was made to expose the interfaces in ShadowRealms, which are currently unlikely to happen. However, we should be consistent and the WebAssembly interfaces are implemented directly in the JS engine rather than on the DOM side in all browsers I'm aware of, so should be exposed in any random realm anyway.

@Ms2ger
Ms2ger merged commit 2e44bf7 into WebAssembly:main Oct 2, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants