Contact emails
zhoupeng.1...@bytedance.com

Explainer
https://github.com/w3c/reporting/issues/263
https://github.com/WICG/crash-reporting/issues/24
https://github.com/WICG/crash-reporting/pull/30


Specification
https://wicg.github.io/crash-reporting/#crash-reports-delivery-priority


Design docs

https://github.com/WICG/crash-reporting/pull/30


Summary

This feature lets you send crash reports only. By default, crash reports are 
delivered to the `default` endpoint which receives many other kinds of reports 
besides crash reports. Developers can supply a separate URL to the well-known 
endpoint named `crash-reporting`, to direct crash reports there, instead of the 
`default` endpoint. See 
https://wicg.github.io/crash-reporting/#crash-reports-delivery-priority.



Blink component
Blink


Motivation

Developers report needing to receive crash reports exclusively. Currently, all 
crash reports are delivered to the endpoint named default with no override 
option. Developers are forced to receive not only crash reports but also 
unrelated reports like `Deprecated feature usage`.



Initial public proposal
https://github.com/WICG/crash-reporting/pull/30


TAG review
As this is a trivial API addition with no impact on default behavior, a TAG 
review is unnecessary.


TAG review status
Pending


Risks




Interoperability and Compatibility

None


Gecko: Positive https://github.com/mozilla/standards-positions/issues/288

WebKit: No signal

Web developers: Positive (https://github.com/w3c/reporting/issues/263)

Other signals:


Security

This feature only adds a way to report crash reports exclusively. Therefore, we 
believe there are no security concerns.



WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it 
has potentially high risk for Android WebView-based applications?

None




Debuggability

None



Is this feature fully tested by web-platform-tests?
No
crash-reporting isn't covered by WPT at present. WPT doesn't support crashing 
the renderer process for contrived reasons like OOM, unresponsiveness.



Flag name on about://flags
None


Finch feature name
OverrideCrashReportingEndpoint


Requires code in //chrome?
False


Tracking bug
https://issues.chromium.org/issues/414723480


Estimated milestones


Shipping on desktop 139

Shipping on Android 139

Shipping on WebView 139




Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5129218731802624?gate=5157964008390656


This intent message was generated by Chrome Platform Status.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68408874.170a0220.190b19.0101.GAE%40google.com.

Reply via email to