← back to v141 · stop-sending-purpose-prefetch-header-from-prefetches-and-prerenders
conformance · v141
v141 · stop-sending-purpose-prefetch-header-from-prefetches-and-prerenders — 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 |
|---|---|---|---|---|
sec-purpose-header-readable |
Headers API can hold a Sec-Purpose value; Sec-Purpose is the replacement header that prefetches/prerenders continue to send. | script | … | |
link-rel-prefetch-supported |
HTMLLinkElement.rel can be set to 'prefetch'; the removed header was previously attached to these fetches. | script | … | |
speculation-rules-script-type |
<script type="speculationrules"> is recognised; the legacy Purpose header was also sent on speculation-rules fetches before the removal. | script | … | |
fetch-with-headers-init |
fetch accepts a headers init; servers detect the new world by reading Sec-Purpose, not Purpose. | script | … | |
document-prerendering |
document.prerendering is exposed; prerendered documents are the scope of the header change. | script | … | |
purpose-prefetch-string-is-not-special |
Headers can still carry a custom 'purpose' value; the change is browser-side (not sending it automatically), not a Headers API change. | script | … |