← back to v142 · local-network-access-restrictions-for-websockets
conformance · v142
v142 · local-network-access-restrictions-for-websockets — 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 |
|---|---|---|---|---|
websocket-constructor |
The WebSocket constructor is exposed; LNA restrictions gate connections from this constructor, they do not remove it. | exists | … | |
secure-context |
The LNA permission is restricted to secure contexts; the page must be HTTPS or localhost. | script | … | |
permissions-api-exists |
navigator.permissions is exposed so userland can probe the local-network / loopback-network permissions. | script | … | |
websocket-readystate-enum |
WebSocket exposes the CONNECTING/OPEN/CLOSING/CLOSED constants so userland can observe the connection state including LNA-gated failures. | script | … | |
close-event-on-websocket |
WebSocket dispatches a CloseEvent when a connection is denied (e.g. by LNA permission); CloseEvent is exposed. | exists | … | |
ws-url-with-loopback-constructible |
Constructing a WebSocket with a loopback URL does not synchronously throw; LNA gating happens during the handshake, not at constructor time. | script | … |