New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testharness.js: fix shadow realm detection #33668
testharness.js: fix shadow realm detection #33668
Conversation
This commit fixes shadow realm detection to not falsely discover the Deno main thread as a shadow realm. Because there is no reliable way to discover shadow realms in isolation, we add a a special global to inform testharness.js that it is running in a ShadowRealm.
Sorry again for the breakage--I had been hoping to avoid adding anything to the global object to signal the test environment is a ShadowRealm but it seems like it's probably the best way after all. Thanks :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we'll need at least a change to resources/idlharness-shadowrealm.js
as well
This reverts commit ce3cb95.
This commit fixes shadow realm detection to not falsely discover the Deno main thread as a shadow realm. Because there is no reliable way to discover shadow realms in isolation, we add a a special global to inform testharness.js that it is running in a ShadowRealm.
This commit fixes shadow realm detection to not falsely discover the
Deno main thread as a shadow realm. Because there is no reliable way to
discover shadow realms in isolation, we add a a special global to inform
testharness.js that it is running in a ShadowRealm.
cc @jjgriego @Ms2ger