← back to v149 · webassembly-custom-descriptors
conformance · v149
v149 · webassembly-custom-descriptors — conformance probe
6 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
webassembly-namespace-exists |
The WebAssembly global namespace is exposed. spec ↗ | exists | … | |
webassembly-module-exists |
WebAssembly.Module constructor is exposed (used to load modules with custom descriptors). spec ↗ | exists | … | |
webassembly-validate-supports-typed-funcref |
WebAssembly.validate accepts the smallest valid module (proxy for tooling pipeline). spec ↗ | script | … | |
webassembly-instance-exists |
WebAssembly.Instance is exposed (the host object whose prototype is configured by custom descriptors). spec ↗ | exists | … | |
webassembly-suspending-or-promising-still-present |
Earlier JS-promise integration surfaces (WebAssembly.Suspending) remain — custom descriptors are additive. spec ↗ | script | … | |
webassembly-compile-streaming-exists |
WebAssembly.compileStreaming still exists — streaming compilation works with descriptors. spec ↗ | typeof | … |