Intent to Extend Experiment: Crash Reporting key-value API

[Chromestatus]

Contact emails

d...@chromium.org

Explainer

https://github.com/WICG/crash-reporting/blob/gh-pages/crashReport-explainer.md

Specification

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

Summary

A new key-value API, tentatively `window.crashReport`, backed by a per-Document map holding data that gets appended to crash reports. See https://github.com/WICG/crash-reporting/issues/15 for initial discussion. The data placed in this API's backing map gets sent in the `CrashReportBody` [1] if any renderer process crashes are incurred by the site. This lets developers debug what specific state in their application might be causing a given crash. [1]: https://wicg.github.io/crash-reporting/#crashreportbody

Blink component

Blink>ReportingObserver

Web Feature ID

None

TAG review

None

TAG review status

Pending

Origin Trial Name

CrashReportingStorageAPI

Chromium Trial Name

CrashReportingStorageAPI

Origin Trial documentation link

https://github.com/WICG/crash-reporting/blob/gh-pages/crashReport-explainer.md

WebFeature UseCounter name

WebDXFeature::kCrashReportStorageAPIInitialize

Risks

Interoperability and Compatibility

None

Gecko: No signal (https://github.com/mozilla/standards-positions/issues/1271)

WebKit: No signal (https://github.com/WebKit/standards-positions/issues/528)

Web developers: Positive First-party partners at Google are excited to be able associate specific app state & data with web-exposed crash reports.

Other signals:

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

Goals for experimentation

Reason this experiment is being extended

Our partners were late to implementing their end of using the feature, so we'd like to extend the OT to give more time for data collection and usage.

Ongoing technical constraints

None

Debuggability

None

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?

Yes

Is this feature fully tested by web-platform-tests?

No
This feature is not fully testable with Web Platform Tests, because WPT infrastructure does not provide the ability to crash specific renderer processes. This limitation has not prevented the Crash Report Infrastructure from shipping in general, nor has it prevented additions like https://chromestatus.com/feature/4731248572628992. This API will be tested with as many web platform tests as possible to assert the shape and semantics of the JS-exposed web API.

Flag name on about://flags

CrashReportingStorageAPI

Finch feature name

CrashReportingStorageAPI

Requires code in //chrome?

False

Tracking bug

https://issues.chromium.org/issues/400432195

Estimated milestones

Origin trial desktop first	140
Origin trial desktop last	142
Origin trial extension 1 end milestone	145
Origin trial Android first	140
Origin trial Android last	142
Origin trial WebView first	140
Origin trial WebView last	142

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/6228675846209536?gate=6010112711983104

Links to previous Intent discussions

Intent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/687500b2.170a0220.1c6204.01c6.GAE%40google.com
Intent to Experiment: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/688a7245.2b0a0220.35091d.043b.GAE%40google.com

This intent message was generated by Chrome Platform Status.

[Vladimir Levin]

LGTM

[Vladimir Levin]

To clarify, the above LGTM is to extend the experiment to 145 inclusive