← back to v139 · re-sizing-tcp-connection-pool
conformance · v139
v139 · re-sizing-tcp-connection-pool — conformance probe
10 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
10
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
fetch-exposed |
fetch() remains exposed; the TCP pool experiment is below the Fetch API surface. | typeof | … | |
xhr-exposed |
XMLHttpRequest remains exposed for legacy clients sharing the same browser socket pools. | typeof | … | |
websocket-exposed |
WebSocket is exposed; ChromeStatus says normal and WebSocket global socket limits are both studied. | typeof | … | |
performance-resource-timing-supported |
PerformanceResourceTiming is exposed for observing connection timing and reuse signals. | typeof | … | |
resource-timing-has-connect-fields |
PerformanceResourceTiming exposes connectStart and connectEnd timing fields. spec ↗ | script | … | |
same-origin-fetch-produces-resource-entry |
A same-origin fetch produces a resource timing entry with numeric duration and connect fields. spec ↗ | script | … | |
performance-get-entries-by-type |
performance.getEntriesByType is available for reading resource timing entries. | typeof | … | |
no-global-setmaxsockets-api |
The browser does not expose a JS-visible setMaxSockets() TCP pool-size setter. | script | … | |
no-navigator-connection-pool-api |
navigator does not expose a connectionPool object for reading or changing the global TCP socket pool. | script | … | |
navigator-connection-effective-type-when-present |
When Network Information is present, effectiveType remains a connection signal independent of pool sizing. | script | … |