Not trivially. You could look for specs that have `object` or `any` (or sequences thereof) return values. And specs with `Promise>` 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>` bits, not all of which actually invoke the WebIDL algorithm) is: * https://w3c.github.io/ServiceWorker/#clients-getall (rather broken; creates array objects in parallel steps, _manipulates_ array objects in parallel steps; filed ). * https://w3c.github.io/ServiceWorker/#dom-cache-keys step 5.4.3 * https://w3c.github.io/ServiceWorker/#dom-cachestorage-keys * https://w3c.github.io/ServiceWorker/#cache-matchall -- specifies the realm, nice! * getFilesAndDirectories in http://w3c.github.io/filesystem-api/ (not directly linkable?)

https://drafts.csswg.org/css-font-loading/#dom-fontfaceset-load

activeVRDisplays (Can't find a spec draft for this)

https://w3c.github.io/ServiceWorker/#navigator-service-worker-getRegistrations (filed getRegistrations manipulates ES arrays in parallel steps w3c/ServiceWorker#1241)

https://notifications.spec.whatwg.org/#dom-serviceworkerregistration-getnotifications sort of (filed getNotifications manipulates ES arrays in parallel steps notifications#113)

"converting to an ECMAScript value" needs to take a realm, at least sometimes #371

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions