← back to v154 · webtransport-headers-and-responseheaders
conformance · v154
v154 · webtransport-headers-and-responseheaders — conformance probe
7 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
7
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
webtransport-available |
The interface this feature extends. spec ↗ | typeof | … | |
options-dictionary-is-read-at-construction |
WebTransportOptions is converted synchronously in the constructor, before any network work. A getter on a declared member must therefore run — this is the control that makes every other dictionary probe meaningful, and serverCertificateHashes has been declared since WebTransport shipped. spec ↗ | script | … | |
undeclared-members-are-never-read |
A dictionary conversion touches only the members it declares. A getter for an invented member must never run, otherwise a member coming back 'not read' would carry no information. spec ↗ | script | … | |
headers-member-is-read |
The request half of the feature: WebTransportOptions declares headers, so the constructor reads it. A build that does not read it cannot carry credentials in the CONNECT. spec ↗ | script | … | |
response-headers-on-prototype |
The response half of the feature: the server's reply to the CONNECT is exposed as an attribute on WebTransport, so it is readable once the session is established. spec ↗ | exists | … | |
forbidden-names-are-dropped-by-the-request-guard |
Header names a page may not set are removed by the request guard rather than raising — the same rule these headers inherit. A bare Headers object has no guard and is not evidence of anything here. spec ↗ | script | … | |
header-values-are-byte-strings |
A header value must be encodable as bytes. A code point above U+00FF throws rather than being mangled, which is why a token pasted with a typographic ellipsis fails loudly instead of arriving corrupted. spec ↗ | script | … |