← back to v139 · fetch-retry-for-keepalive-fetches
conformance · v139
v139 · fetch-retry-for-keepalive-fetches — 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-exposed |
fetch() is exposed in window context. | typeof | … | |
request-constructor |
Request constructor is exposed; the retry / keepalive options live on the RequestInit dictionary it accepts. | typeof | … | |
keepalive-option-accepted |
Constructing a Request with {keepalive: true} reflects back as request.keepalive === true. spec ↗ | script | … | |
retry-option-does-not-throw |
Constructing a Request with a `retry` option dictionary should not throw — Chrome 139 expands RequestInit with a retry knob for keepalive fetches. | script | … | |
request-headers-still-work |
request.headers is exposed; the keepalive+retry pipeline still uses the standard Headers object. | script | … | |
navigator-sendbeacon-still-exposed |
navigator.sendBeacon is still exposed; fetch+keepalive+retry is the modern replacement but sendBeacon remains for now. | typeof | … |