RESOLVED CONFIGURATION CHANGED 189365
Feature Request: W3C Reporting API 
https://bugs.webkit.org/show_bug.cgi?id=189365
Summary Feature Request: W3C Reporting API
Renaud Chaput
Reported 2018-09-06 12:51:49 PDT
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, ...).
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2022-06-30 16:50:02 PDT
<rdar://problem/96255218>
Anne van Kesteren
Comment 2 2025-01-07 02:17:21 PST
By-and-large this is done.
Note You need to log in before you can comment on or make changes to this bug.