Repository navigation
Expose some Web APIs on ShadowRealms #331
Description
Meta issue - relevant changes will be made to the Web specs.
- Expose everywhere w3c/hr-time#130
- Expose everywhere w3c/performance-timeline#193
- Expose everywhere w3c/resource-timing#302
- Expose everywhere w3c/server-timing#84
- Expose everywhere w3c/user-timing#85
- Expose everywhere whatwg/console#209
- Expose events/aborts everywhere whatwg/dom#1024
- Expose everywhere whatwg/encoding#274
- Expose Error/PromiseRejectionEvent everywhere whatwg/html#7244
- Expose everywhere whatwg/streams#1176
- Expose URL/URLSearchParams everywhere whatwg/url#657
- Expose everywhere whatwg/compression#40
- Expose everywhere WICG/scheduling-apis#51
- [js-api] Expose everywhere WebAssembly/spec#1550
Reacted by Leo Balter, Kenta Moriuchi, lin72h, EviSONG and Sam Maddock
Reacted by lin72h
Reacted by lin72h and Sam Maddock
Reacted by lin72h
Activity
Expose URL/URLSearchParams everywhere
Ms2ger commentedon Oct 12, 2021
Depends on whatwg/webidl#526
Expose events/aborts everywhere
Expose the JS API everywhere
Expose events/aborts everywhere
annevk commentedon Oct 14, 2021
This has implementer interest, so I'm thinking that once there are tests and there's bugs filed, we merge all the relevant WHATWG PRs together. Does that seem reasonable?
cc @domenic @padenot @codehag
codehag commentedon Oct 14, 2021
That sounds reasonable to me.
Expose everywhere
Expose everywhere
Expose everywhere
Expose everywhere
Expose everywhere
Expose everywhere
Expose everywhere
Expose everywhere
25 remaining items
Bug 1754788 [wpt PR 32800] - Add tests for Web APIs in ShadowRealms.,…
Add tests for Web APIs in ShadowRealms. (web-platform-tests#32800)
Bug 1754788 [wpt PR 32800] - Add tests for Web APIs in ShadowRealms.,…
Bug 1754788 [wpt PR 32800] - Add tests for Web APIs in ShadowRealms.,…
Bug 1754788 [wpt PR 32800] - Add tests for Web APIs in ShadowRealms.,…
Expose ErrorEvent and PromiseRejectionEvent everywhere
littledan commentedon Jun 7, 2022
It looks like all of the relevant PRs to various specs have landed, with the sole exception of console (just blocking on manual tests--maybe we should just push back on that request). The only thing I see missing is some machinery in WebIDL: I don't think these APIs are actually exposed to ShadowRealm at the moment, as ShadowRealm is not an interface. We should probably add some plumbing in WebIDL to handle it specially.
annevk commentedon Jun 8, 2022
I think it would be better to make the relevant requirements in HTML, as that already deals with most of the globals of the web platform and integration with ShadowRealm.
Expose everywhere
littledan commentedon Jun 23, 2022
@annevk How would this be handled in HTML? I explained the concrete problem here; it's hard for me to imagine the fix coming in HTML without HTML reaching rather deep into WebIDL.
Ms2ger commentedon Aug 8, 2022
Everything I wanted to do in this issue is done.
BadassGhost commentedon Jul 16, 2023
Bug 1754788 [wpt PR 32800] - Add tests for Web APIs in ShadowRealms.,…
Bug 1754788 [wpt PR 32800] - Add tests for Web APIs in ShadowRealms.,…