← back to v130 · attribution-reporting-api-feature-debug-key-privacy-improvement
conformance · v130
v130 · attribution-reporting-api-feature-debug-key-privacy-improvement — 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 |
|---|---|---|---|---|
attribution-reporting-api-present |
The browser exposes the Attribution Reporting API surface this change applies to (HTMLAnchorElement.attributionSrc). spec ↗ | script | … | |
third-party-cookies-status-readable |
navigator.cookieEnabled is exposed, since the debug-key privacy gate depends on third-party cookie availability. | typeof | … | |
has-storage-access-api |
document.hasStorageAccess is exposed; debug-key gating is in the same cross-site cookie privacy regime. | typeof | … | |
attribution-reporting-eligible-header-name-recognised |
The Attribution-Reporting-Eligible request header name (whose responses can carry debug_key) is acceptable to Headers. spec ↗ | script | … | |
debug-cookie-name-defined |
Debug keys are gated by the ar_debug cookie; the cookie store API must be available for sites to probe its presence. spec ↗ | exists | … |