[Webkit-unassigned] [Bug 189365] New: Feature Request: W3C Reporting API

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=189365

            Bug ID: 189365
           Summary: Feature Request: W3C Reporting API
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: All
                OS: All
            Status: NEW
          Severity: Enhancement
          Priority: P2
         Component: New Bugs
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: renchap at gmail.com

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, ...).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180906/f97ef754/attachment.html>