WPT
wpt / wasm / jsapi / esm-integration / global-exports.tentative.any.worker.html
Spec: WebAssembly JavaScript Interface ↗
Runs: Chrome 155.0.8041.0 (wpt@2c385f65e, 2026-09-04) | Firefox 157.0a1 (wpt@2c385f65e, 2026-09-04) | Safari 251 preview (wpt@5ce815a83, 2026-08-27) | Ladybird 1.0-a7825 (wpt@2c385f65e, 2026-09-04) | Servo Servo 0.6 (wpt@7e3d005d7, 2026-09-03) | Blitz a50cb8971 (wpt@a95401e4e, 2026-09-03)
View on the Blitz WPT dashboard | Open test on wpt.live | wpt.fyi
| Chrome | Firefox | Safari | Ladybird | Servo | Blitz | |
|---|---|---|---|---|---|---|
| Total | 0/5 | 0/5 | 0/5 | 0/5 | 0/5 | NOT RUN |
| Subtest | Chrome | Firefox | Safari | Ladybird | Servo | Blitz |
|---|---|---|---|---|---|---|
| WebAssembly module global values should be unwrapped when importing in ESM integration | FAIL | FAIL | FAIL | FAIL | FAIL | — |
| WebAssembly mutable global values should be unwrapped when importing in ESM integration | FAIL | FAIL | FAIL | FAIL | FAIL | — |
| WebAssembly local global values should be unwrapped when exporting in ESM integration | FAIL | FAIL | FAIL | FAIL | FAIL | — |
| WebAssembly module globals from imported WebAssembly modules should be unwrapped | FAIL | FAIL | FAIL | FAIL | FAIL | — |
| WebAssembly should properly handle all global types | FAIL | FAIL | FAIL | FAIL | FAIL | — |