← back to v132 · attribution-reporting-api-feature-change-to-ar-debug-cookie-requirement

conformance · v132

v132 · attribution-reporting-api-feature-change-to-ar-debug-cookie-requirement — 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.

browser: spec: https://wicg.github.io/attribution-reporting-api/#attribution-debugging chromestatus: #5107034180288512 generated 2026-06-02T08:32:29Z by conformance-author-codex
0
pass
0
fail
0
blocked
5
total
id contract kind verdict detail
attribution-src-on-anchor HTMLAnchorElement.attributionSrc is the registration surface affected by debug reporting. spec ↗ script
navigator-cookieenabled-boolean navigator.cookieEnabled is exposed because debug mode depends on cookie availability. typeof
storage-access-api-exposed document.hasStorageAccess is exposed for the third-party cookie privacy regime debug mode interacts with. typeof
ar-debug-cookie-can-be-addressed A same-site ar_debug cookie can be set and cleared by normal cookie mechanics. spec ↗ script
verbose-debug-header-name-accepted Headers accepts Attribution-Reporting-Register-Trigger payloads that can contain debug reporting fields. spec ↗ script