Closed Bug 1489431 Opened 6 years ago Closed 6 years ago

Implement W3C Reporting API

Categories

(Core :: DOM: Core & HTML, enhancement)

Product:
Core
Component:
DOM: Core & HTML
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1492036

People

(Reporter: renchap, Unassigned)

Details

W3C spec draft: https://w3c.github.io/reporting/

Abstract: This document defines a generic reporting framework which allows web developers to associate a set of named reporting endpoints with an origin. Various platform features (like Content Security Policy, Network Error Reporting, and others) will use these endpoints to deliver feature-specific reports in a consistent manner.

Some examples on Chrome's blog:
- https://developers.google.com/web/updates/2018/07/reportingobserver
- https://developers.google.com/web/updates/2018/09/reportingapi

ReportingObserver shipped in Chrome 69, the Report-To Header is currently behind a flag in Chrome

This creates a standard way to report any problem with a page to the website's owner, replacing the various current mechanisms (catching JS exceptions at the root, CSP reports, …) and allows the reporting of more issues that can not currently be captured (deprecation notices, network errors, ...).
Component: General → DOM
Product: Firefox → Core
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(amarchesini)
Resolution: --- → DUPLICATE
Clearing needinfo, discussed on irc.
Flags: needinfo?(amarchesini)
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.