← back to v131 · direct-sockets-api
conformance · v131
v131 · direct-sockets-api — 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 |
|---|---|---|---|---|
tcpsocket-interface-exposed |
The TCPSocket constructor is exposed in Isolated Web App contexts that have direct-sockets enabled. spec ↗ | script | … | |
udpsocket-interface-exposed |
The UDPSocket constructor is exposed for datagram communication. | script | … | |
tcpserversocket-interface-exposed |
The TCPServerSocket constructor is exposed for accepting incoming TCP connections. | script | … | |
permissions-policy-direct-sockets |
direct-sockets is gated by the direct-sockets Permissions-Policy feature. | script | … | |
tcpsocket-not-exposed-in-normal-page |
TCPSocket is not exposed in a normal (non-IWA, non-flag-enabled) page so regular sites cannot scan the LAN. | script | … |