← back to v150 · deprecate-and-remove-attribution-reporting-api
conformance · v150
v150 · deprecate-and-remove-attribution-reporting-api — conformance probe
6 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
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
attribution-reporting-removed |
Document.featurePolicy or document.permissionsPolicy no longer lists 'attribution-reporting' as an allowed feature — the API is removed in Chrome 150. | script | … | |
attributionreporting-attribute-removed |
The 'attributionsrc' content attribute is no longer reflected on <a> elements as an IDL property. | script | … | |
registerattributionsource-removed |
navigator.registerAttributionSource is no longer present on Navigator (where it was historically considered). | script | … | |
fetch-still-works |
fetch() still works — only the attributionreporting-specific surfaces are removed, not the underlying network APIs. | typeof | … | |
iframe-attributionsrc-not-reflected |
HTMLIFrameElement no longer reflects an attributionSrc IDL attribute. | script | … | |
attribution-reporting-eligible-not-special |
Setting an 'Attribution-Reporting-Eligible' header via Request is allowed (header is no longer special-cased) — fetch construction succeeds. | script | … |