Conversation
…ace in this namespace
Ms2ger
approved these changes
Oct 2, 2026
Ms2ger
left a comment
Collaborator
There was a problem hiding this comment.
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#1550 exposed every interface in the
WebAssemblynamespace everywhere (Exposed=*), butTagandExceptionpredate 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)