Intent to implement: Crash Reports (via Reporting API)
Paul Meyer
Contact emails
Explainer
https://github.com/w3c/reporting/blob/master/EXPLAINER.md#crashes
Spec
https://w3c.github.io/reporting/#crash-report
Summary
Crash reports are a new type of report to be routed into the Reporting API backend. These reports will indicate to developers that a crash has occurred on their page (and possibly, for what reason, i.e. OOM).
Motivation
Crash reporting adds to the sphere of information that developers will be able to receive via Reporting API.
Interoperability and Compatibility Risk
No change in existing behavior, so compatibility risk should be very low. Interoperability risk is also very low, since the design says nothing about when crashes will occur (as ideally, they never should). The only requirement is that for those reports that are generated, they must conform to a specific format.
Debuggability
No changes required.
Discussions:
https://github.com/w3c/reporting/issues/44
https://github.com/w3c/reporting/issues/55
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes.
Link to entry on the feature dashboard
https://www.chromestatus.com/feature/5643666605473792 b
Requesting approval to ship?
No.