Bug 189365

Summary:	Feature Request: W3C Reporting API
Product:	WebKit	Reporter:	Renaud Chaput <renchap>
Component:	New Bugs	Assignee:	Nobody <webkit-unassigned>
Status:	NEW ---
Severity:	Enhancement	CC:	agektmr, bfulgham, m.goleb+bugzilla, webkit-bug-importer
Priority:	P2	Keywords:	InRadar
Version:	WebKit Nightly Build
Hardware:	All
OS:	All
Bug Depends on:	244368, 244517, 243908, 244143, 244369, 244689, 244719, 244905, 244907, 245197, 245368
Bug Blocks:	244899

Description Renaud Chaput 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, ...).

Comment 1 Radar WebKit Bug Importer 2022-06-30 16:50:02 PDT

<rdar://problem/96255218>