← back to v144 · deprecate-and-remove-attribution-reporting-api
conformance · v144
v144 · deprecate-and-remove-attribution-reporting-api — conformance probe
4 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
4
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
attributionreporting-attr-removed |
The attributionreporting content attribute on <a> and <img> no longer functions; navigator.attributionReporting is undefined. spec ↗ | script | … | |
attribution-reporting-fetch-option-rejected |
fetch() with an attributionReporting option no longer triggers any registration; the option is silently ignored. Testable: the option name is not enumerated on Request prototype. spec ↗ | script | … | |
permissions-policy-attribution-reporting-removed |
The 'attribution-reporting' permissions-policy feature is no longer enumerated. spec ↗ | script | … | |
no-window-fence-reporter |
window.fence (where attribution events could be reported from a fenced frame) is undefined in normal documents. spec ↗ | script | … |