"converting to an ECMAScript value" needs to take a realm, at least sometimes #371
Comments
So for the uses in the IDL spec itself, there is always a current Realm, I believe. But I agree, for uses from other specs something needs to happen. |
Is there a way to find out which specs call the "convert to an ECMAScript value" algorithm, other than Web IDL itself? |
Not trivially. You could look for specs that have It's not even trivial to tell from implementations, I suspect. In Gecko promises will automatically pick a global based on various criteria when you resolve them with something... That said, a non-exhaustive list (just
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
E.g. if you convert a
sequence<DOMString>
to an array, you need to specify the realm/global in which the conversion happens.Related: w3ctag/promises-guide#52 (comment)
The text was updated successfully, but these errors were encountered: