Crash Reporting API: is_top_level & visibility_state

Category: Miscellaneous
Type: New or changed feature
Status: Proposed (Chrome Proposed)
Intent stage: None

Summary

This feature adds `is_top_level` and `visibility_state` string fields to the crash reporting API body that gets sent to the default reporting endpoint for crash reports. See https://wicg.github.io/crash-reporting/#crash-report. For `is_top_level`: see https://github.com/WICG/crash-reporting/issues/20 & https://github.com/WICG/crash-reporting/pull/23. The string value "true" or "false" is included depending on whether the Document sending the crash report belongs to a top-level traversable navigables. For `visibility_state`: see https://github.com/WICG/crash-reporting/issues/14#issuecomment-2452393164.

Motivation

We've gotten reports from many developers that it would be useful to include more contextual bits of information about a crashing frame in the crash report body that gets sent to the `default` reporting endpoint. This feature exposes two new bits of information that were explicitly requested: `is_top_level` and `page_visibility`. See https://github.com/WICG/crash-reporting/issues/20 and https://github.com/WICG/crash-reporting/issues/14.

Standards & signals

Specification: https://github.com/WICG/crash-reporting/pull/23
Firefox: Positive — I marked this as positive because the entire crash reporting API was marked as supportive by Mozilla in https://github.com/mozilla/standards-positions/issues/288, and Martin pointed to that when I filed a more specific one for these two small additions.
Safari: No signal
Web developers: Positive — Internal partners are very happy to receive this kind of new information in the crash report JSON body.

Docs: https://github.com/WICG/crash-reporting/pull/23

Explainers: https://github.com/WICG/crash-reporting/issues/20 https://github.com/WICG/crash-reporting/issues/14 https://github.com/WICG/crash-reporting/pull/23

View on chromestatus.com