← back to v132 · fenced-frames-send-referer-header-in-beacons
conformance · v132
v132 · fenced-frames-send-referer-header-in-beacons — 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 |
|---|---|---|---|---|
fencedframe-element-interface |
HTMLFencedFrameElement is exposed as the element interface for fenced frames. spec ↗ | exists | … | |
fencedframe-element-creatable |
document.createElement('fencedframe') creates an HTMLElement for feature detection. spec ↗ | script | … | |
fence-global-probe |
The fenced frame reporting API is detectable via a window.fence object when available. spec ↗ | script | … | |
headers-accept-referer-name |
Headers accepts the Referer header name used by fenced frame reporting beacons. spec ↗ | script | … | |
referrer-policy-property-exposed |
Request.prototype.referrerPolicy is exposed because beacon Referer emission is governed by referrer policy. spec ↗ | script | … |