WPT details: There are no web platform tests for this tiny addition to the crash reporting API, because the crash reporting API itself cannot be tested this way at the moment. WPTs do not support crashing the renderer process for a contrived set of reasons (OOM, unresponsiveness, etc). Note that this has been documented in all of the other parts of this API that have shipped. See https://groups.google.com/a/chromium.org/g/blink-dev/c/tgRcEnqIb1A, for example.
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.
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.
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