← back to v143 · tcp-socket-pool-limit-randomization
conformance · v143
v143 · tcp-socket-pool-limit-randomization — 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 |
|---|---|---|---|---|
fetch-exists |
fetch() is exposed — the side-channel concern lives at the connection layer below fetch. spec ↗ | typeof | … | |
abortcontroller-exists |
AbortController is exposed so tests can hold/release sockets without leaks. spec ↗ | typeof | … | |
performance-resource-timing |
PerformanceResourceTiming exposes connectStart/connectEnd — the bus authors used to fingerprint the pool. spec ↗ | script | … | |
performance-now-available |
performance.now is available — needed to measure socket-pool exhaustion timing. spec ↗ | typeof | … | |
reporting-observer-available |
ReportingObserver exists — networking changes that opt-in deprecation reports can surface via it. spec ↗ | exists | … | |
navigator-online |
navigator.onLine is exposed — useful when socket pool changes cause perceived offline-like behavior in tests. spec ↗ | script | … |