189365 2018-09-06 12:51:49 -0700 Feature Request: W3C Reporting API 2025-01-07 02:17:21 -0800 1 1 1 Unclassified WebKit New Bugs WebKit Nightly Build All All RESOLVED CONFIGURATION CHANGED InRadar P2 Enhancement --- 244368 243908 244143 244369 244517 244689 244719 244905 244907 245197 245368 244899 1 renchap webkit-unassigned agektmr annevk bfulgham marcosc m.goleb+bugzilla webkit-bug-importer oldest_to_newest 1457194 0 renchap 2018-09-06 12:51:49 -0700 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, ...). 1879592 1 webkit-bug-importer 2022-06-30 16:50:02 -0700 <rdar://problem/96255218> 2085365 2 annevk 2025-01-07 02:17:21 -0800 By-and-large this is done.