← back to v154 · support-targetaddressspace-option-for-websockets
conformance · v154
v154 · support-targetaddressspace-option-for-websockets — conformance probe
5 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
5
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
constructor-reads-targetaddressspace |
The feature: the WebSocket constructor must read a targetAddressSpace member from its options dictionary. Probed with a getter, so no connection or permission prompt is involved. spec ↗ | script | … | |
fetch-already-supports-targetaddressspace |
fetch() has had the option for a while; WebSockets is catching up. Asserting the fetch side pins the reference point rather than assuming it, and shows the two are meant to match. spec ↗ | script | … | |
invalid-address-space-is-rejected |
targetAddressSpace is an enum of loopback, local and public. A value outside it must be a TypeError at construction — a typo should be a bug you find, not a permission you silently never get. spec ↗ | script | … | |
options-bag-is-the-carrier |
This option can only exist because the constructor takes a dictionary, so the two features are asserted together: if protocols is not read from a dictionary, targetAddressSpace cannot be either. spec ↗ | script | … | |
same-origin-connection-still-opens |
The control: a same-origin socket must still open normally. Without this the other assertions cannot be interpreted. spec ↗ | script | … |