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 ensures developers receive only crash reports by specifying the endpoint named `crash-reporting `. 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.
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`.
Docs: https://github.com/WICG/crash-reporting/pull/30
Explainers: https://github.com/w3c/reporting/issues/263 https://github.com/WICG/crash-reporting/issues/24 https://github.com/WICG/crash-reporting/pull/30