-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Test entry and incumbent settings object for promise jobs #21206
Conversation
…ent. Finally made Chrome fail.
...cripting/processing-model-2/integration-with-the-javascript-job-queue/promise-job-entry.html
Show resolved
Hide resolved
...ting/processing-model-2/integration-with-the-javascript-job-queue/promise-job-incumbent.html
Outdated
Show resolved
Hide resolved
...ting/processing-model-2/integration-with-the-javascript-job-queue/promise-job-incumbent.html
Outdated
Show resolved
Hide resolved
|
||
const thenable = { | ||
// No t.step_func because that could change the realms | ||
then(f) { |
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.
Somewhere around here should we have a test where the then
function of the thenable is effectively a scripted function from the incumbent global (perhaps runWindowPostMessageVeryIndirectly
bound to some args)? Maybe it doesn't matter too much....
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'm not sure I quite understand what this adds over the (2) suggested above (where the then
function is from a different realm). Is using the incumbent global in particular important?
Firefox is kinda whiny without them
Substantially based on #21206. Ref: WebAssembly/spec#1184.
Substantially based on #21206. Ref: WebAssembly/spec#1184.
Substantially based on #21206. Ref: WebAssembly/spec#1184.
Follows whatwg/html#5212 which specifies entry, and throws in incumbent tests for good measure while we're here.
Chrome and Firefox both seem to pass these, which is somewhat surprising.