← back to v135 · fenced-frames-automatic-beacon-cross-origin-data-support
conformance · v135
v135 · fenced-frames-automatic-beacon-cross-origin-data-support — 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 |
|---|---|---|---|---|
html-fenced-frame-element-exists |
HTMLFencedFrameElement is exposed on the global. spec ↗ | exists | … | |
fence-or-fenceapi-exposed |
window.fence (or the Fence interface) is exposed inside a fenced frame for setting reporting data. spec ↗ | script | … | |
setreporteventdata-method-shape |
If Fence is exposed, setReportEventDataForAutomaticBeacons is present (the cross-origin data entry point). spec ↗ | script | … | |
fenced-frame-can-be-created |
document.createElement('fencedframe') returns an HTMLFencedFrameElement. spec ↗ | script | … | |
fenced-frame-config-exposed |
FencedFrameConfig is exposed — the configuration object handed to fenced frames. spec ↗ | exists | … |