← back to v145 · tcp-socket-pool-limit-randomization
conformance · v145
v145 · tcp-socket-pool-limit-randomization — 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 |
|---|---|---|---|---|
fetch-still-exists |
fetch is exposed — the surface used for any cross-site fetch the new randomization indirectly affects. | typeof | … | |
performance-resource-timing-exists |
PerformanceResourceTiming is exposed — the timing surface that would expose any observable jitter from connection pool randomization. | exists | … | |
resource-timing-connect-fields |
PerformanceResourceTiming.prototype exposes connectStart/connectEnd — the timings most relevant to socket pool behaviour. | script | … | |
xhr-still-exists |
XMLHttpRequest is exposed — the legacy surface that also routes through the affected socket pools. | exists | … | |
websocket-still-exists |
WebSocket is exposed — another consumer of HTTP connection budgets that the randomization governs. | exists | … |