📊 Reporting API

What is the Reporting API?

The Reporting API allows browsers to report various types of issues back to developers, including:

Deprecation reports — When your code uses a deprecated browser feature
Intervention reports — When the browser blocks an action for user experience
CSP violation reports — Content Security Policy violations
Crash reports — When a tab crashes
Permissions policy reports — Permission policy violations

The ReportingObserver API lets you catch these reports in JavaScript!

ReportingObserver Status

Generate Reports

Click the buttons below to trigger various browser reports. Watch them appear in the log below and in the DevTools Application panel.

Captured Reports

No reports captured yet. Click the buttons above!

Report Types Reference

📋 Deprecation Report

Generated when using a deprecated Web Platform feature. Contains: id, message, sourceFile, lineNumber, anticipatedRemoval date.

🛑 Intervention Report

Generated when the browser intervenes to block something (e.g., blocking an autoplaying video, preventing heavy ads). Contains: id, message.

🔒 CSP Violation Report

Generated when Content Security Policy is violated. Requires server-side Report-To header.

Event Log

🔧 DevTools: Inspecting the Reporting API

Open DevTools → Application panel
Expand Background services → click Reporting API
This panel shows all reports generated by the page
You can filter by report type (deprecation, intervention, etc.)
Click on a report to see its full details
The Console will also show deprecation warnings

📝 Practice Exercise

Open the Reporting API section in the Application panel
Click "Trigger Deprecation Warning" — do reports appear?
Check the Console for deprecation warnings
Click "Check Buffered Reports" to see what ReportingObserver captured
Try the "Trigger Browser Intervention" button — different browser behavior applies
Compare what you see in the Application panel vs. the Console