You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
"converting to an ECMAScript value" needs to take a realm, at least sometimes #371
You could look for specs that have object or any (or sequences thereof) return values. And specs with Promise<sequence<something>> return values. And so on....
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 Promise<sequence<*>> bits, not all of which actually invoke the WebIDL algorithm) is:
Activity
bzbarsky commentedon Jun 21, 2017
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.
TimothyGu commentedon Dec 3, 2017
Is there a way to find out which specs call the "convert to an ECMAScript value" algorithm, other than Web IDL itself?
bzbarsky commentedon Dec 4, 2017
Not trivially.
You could look for specs that have
objectorany(or sequences thereof) return values. And specs withPromise<sequence<something>>return values. And so on....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
Promise<sequence<*>>bits, not all of which actually invoke the WebIDL algorithm) is:activeVRDisplays(Can't find a spec draft for this)