← back to v158 · webtransport-reliability-attributes
conformance · v158
v158 · webtransport-reliability-attributes — conformance probe
9 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
9
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
webtransport-exists |
The WebTransport constructor exists (the reliability attributes extend it, so every other assertion builds on this). spec ↗ | typeof | … | |
reliability-on-prototype |
WebTransport.prototype exposes the reliability attribute. spec ↗ | script | … | |
reliability-readonly-accessor |
reliability is a readonly attribute: an accessor with a getter and no setter on the prototype. spec ↗ | script | … | |
reliability-initially-pending |
A newly constructed (still connecting) WebTransport reports reliability === "pending", per the constructor's [[Reliability]] = "pending" step. spec ↗ | script | … | |
reliability-value-in-enum |
The value read from a live object is one of the WebTransportReliabilityMode enum strings: "pending", "reliable-only", or "supports-unreliable". spec ↗ | script | … | |
supportsreliableonly-static-boolean |
supportsReliableOnly is an own property of the WebTransport constructor (a static attribute) and reads as a boolean. spec ↗ | script | … | |
supportsreliableonly-not-on-instances |
Being static, supportsReliableOnly is not on the prototype, so instances read undefined for it. spec ↗ | script | … | |
reliability-strict-write-throws |
Assigning to reliability on an instance in strict mode throws a TypeError, because the accessor has no setter. spec ↗ | script | … | |
reliability-transitions-on-establishment |
After a session establishes, reliability becomes "supports-unreliable" (HTTP/3) or "reliable-only" (HTTP/2). Establishing a session needs a reachable HTTP/3 WebTransport endpoint, which this static showcase cannot provide. spec ↗ | manual | … |