Specify that returned Promises are created in the relevant realm #598
Conversation
Note that these semantics differ from JavaScript async functions, which create a Promise in the current Realm. Verified in Chromium and Firefox that HTMLImageElement.decode and CustomElementsRegistry.whenDefined return Promise instances from the relevant realm. (I'm not sure what's the preferred way to typeset "this", or if it would be preferred to thread it explicitly through the algorithm. Also, it's not quite necessary to use the relevant Promise.resolve function, since resolve effectively uses the relevant realm of its receiver(!)) Resolves part of whatwg#135
|
We don't have a convention yet for "this", but it would be really great if we made it available on the IDL side of things as well (i.e., for specification algorithms). https://www.w3.org/Bugs/Public/show_bug.cgi?id=27301 requested that a long time ago. #495 adds it, but couples it with other things that were harder to reach agreement on. |
littledan
force-pushed
the
promise-realm
branch
from
6bf0df5
to
688df8c
Compare
|
It seems kinda strange to refer to a |
|
OK, seems like this patch (as well as #595) will need to block on the infrastructure for |
|
Related: #371 |
annevk
added
the
do not merge yet
|
We now have "this". Do you still wish to pursue this? |
|
Note that we don't have this in the "converted to an IDL value" algorithm. I don't think this PR makes a great deal of sense without fixing #371 first. |
|
Let's close this and continue trying for the more ambitious plan in #135 (comment). |
Note that these semantics differ from JavaScript async functions, which
create a Promise in the current Realm.
Verified in Chromium and Firefox that HTMLImageElement.decode and
CustomElementsRegistry.whenDefined return Promise instances from
the relevant realm.
(I'm not sure what's the preferred way to typeset "this", or if it would
be preferred to thread it explicitly through the algorithm. Also, it's
not quite necessary to use the relevant Promise.resolve function, since
resolve effectively uses the relevant realm of its receiver(!))
Resolves part of #135
Preview | Diff