2036160 - Enable Crash Reporting API in Nightly.

Status: RESOLVED FIXED

(Core :: DOM: Security, defect)

Comment 1

[Jeff Muizelaar [:jrmuizel]]

Attachment: Bug 2036160 - Enable Crash Reporting API in Nightly.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/4a05b7036695
https://hg.mozilla.org/integration/autoland/rev/58587d530e29
Enable Crash Reporting API in Nightly.

Comment 3

[amarc]

https://hg.mozilla.org/mozilla-central/rev/58587d530e29

Comment 4

[Hamish Willee]

FF152 MDN docs work for this can be tracked in https://github.com/mdn/content/issues/44297

1. I tested on preview 152 and 153.0a1 (2026-06-01) and the window.crashReport and CrashReportContext are not defined (I can only see the IDL in the test context https://searchfox.org/firefox-main/source/testing/web-platform/tests/interfaces/crash-reporting.idl).

   Am I missing something?

2. Are the reporting endpoints supported, as documented in CrashReport

   Reporting-Endpoints: crash-reporting="https://example.com/reports"
   

   and

   Reporting-Endpoints: default="https://example.com/reports"
   

3. Does the output match the Crash report format as documented https://developer.mozilla.org/en-US/docs/Web/API/CrashReport#instance_properties

   I'm asking because browser compat indicates that crash reports were sent to the endpoints from FF130 in https://github.com/mdn/browser-compat-data/blob/main/http/headers/Reporting-Endpoints.json#L104-L116 - so I am wondering what changed - did the reports just omit the context prior to this release?

4. Is there a way to force a crash to test (in my personal tests scripts I tried allocating all resources etc, but Firefox is remarkably robust).