Intent to Ship: Crash Reports (via Reporting API)

[paul...@chromium.org]

Contact emails

paul...@chromium.org

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

 

Prototype

https://chromium-review.googlesource.com/c/chromium/src/+/1220031

Link to “Intent to Implement” blink-dev discussion

https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/rbqI2wiszyY

Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

Yes.

Risks

No additional risks (beyond that of Reporting API).

Is this feature fully tested by web-platform-tests? Link to test suite results from wpt.fyi.

This feature is tested in Chrome’s browsertests. Currently, these features are not testable via web-platform-tests, but will be once the WebDriver Extension function outlined here is implemented.

Entry on the feature dashboard

https://www.chromestatus.com/feature/6683949661159424

[Ojan Vafai]

LGTM1

[Chris Harrelson]

LGTM2

--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b1478f70-1ccf-441a-ade7-453887e1ae0a%40chromium.org.

[Christian Biesinger]

Is this the current template? I thought there was supposed to be an interior section with signals from other browsers.

--

You received this message because you are subscribed to the Google Groups "blink-dev" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/156588d7-049f-4935-93cc-aa8695383c5e%40chromium.org.

[Daniel Bratell]

LGTM3

/Daniel

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9bH%3DYD9pOgrfNjDOJSOY1A-7i8%2BUDK1NGRaw4LOdV9%3DQ%40mail.gmail.com.

--

/* Opera Software, Linköping, Sweden: CET (UTC+1) */

[Paul Meyer]

Hmm, it's possible I missed that section (I copied this from another intent to ship, rather than from the current template). That being said, that is contained in the Chrome Status entry.

[block.rxc...@gmail.com]

current Deprecation Report is not JSON serializable.

is Crash Report JSON serializable ?

2018年11月7日水曜日 0時40分26秒 UTC+9 paul...@chromium.org:

[block.rxc...@gmail.com]

https://w3c.github.io/reporting/#concept-reports

> Each report has a body, which is either null or an object which can be serialized into a JSON text. 

2018年11月7日水曜日 10時43分03秒 UTC+9 jxck jxck:

[Joe Medley]

Paul,

Do you have a tracking bug? It needs to be in the Status entry.

Joe Medley | Technical Writer, Chrome DevRel | jme...@google.com | 816-678-7195

If an API's not documented it doesn't exist.

--

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+...@chromium.org.

[Philip Jägenstedt]

Hey Paul, thanks for working on the test automation for this feature. May I ask what the current status is? lpz@ has begun looking into streamlining the processes for adding test automation more broadly, and I suspect there are things we can learn from this case.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJUhtG_H1gQiJWxZZXkdFPqmwamauHcJ7YeqF84jzzdLMscECw%40mail.gmail.com.