Bug 2036160 Comment 4 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

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

1. I tested on preview 152/153 and the [`window.crashReport`](https://developer.mozilla.org/en-US/docs/Web/API/Window/crashReport) and [`CrashReportContext`](https://developer.mozilla.org/en-US/docs/Web/API/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).

   Is that to be expected? 
2. Are the reporting endpoints supported, as documented in [`CrashReport`](https://developer.mozilla.org/en-US/docs/Web/API/CrashReport)

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

   ```http
   Reporting-Endpoints: default="https://example.com/reports"
   ```
3. Is there a way to force a crash to test (in my [personal tests scripts](https://github.com/hamishwillee/various_webapi_tests/tree/main/ReportingAPI/crash) I tried allocating all resources etc, but Firefox is remarkably robust).
FF152 MDN docs work for this can be tracked in https://github.com/mdn/content/issues/44297

1. I tested on preview 152/153 and the [`window.crashReport`](https://developer.mozilla.org/en-US/docs/Web/API/Window/crashReport) and [`CrashReportContext`](https://developer.mozilla.org/en-US/docs/Web/API/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).

   Is that to be expected? 
2. Are the reporting endpoints supported, as documented in [`CrashReport`](https://developer.mozilla.org/en-US/docs/Web/API/CrashReport)

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

   ```http
   Reporting-Endpoints: default="https://example.com/reports"
   ```
3. Is there a way to force a crash to test (in my [personal tests scripts](https://github.com/hamishwillee/various_webapi_tests/tree/main/ReportingAPI/crash) I tried allocating all resources etc, but Firefox is remarkably robust).
4. 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 - how is that possible given crash reporting is landing now?
FF152 MDN docs work for this can be tracked in https://github.com/mdn/content/issues/44297

1. I tested on preview 152/153 and the [`window.crashReport`](https://developer.mozilla.org/en-US/docs/Web/API/Window/crashReport) and [`CrashReportContext`](https://developer.mozilla.org/en-US/docs/Web/API/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).

   Is that to be expected? 
2. Are the reporting endpoints supported, as documented in [`CrashReport`](https://developer.mozilla.org/en-US/docs/Web/API/CrashReport)

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

   ```http
   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
4. Is there a way to force a crash to test (in my [personal tests scripts](https://github.com/hamishwillee/various_webapi_tests/tree/main/ReportingAPI/crash) I tried allocating all resources etc, but Firefox is remarkably robust).
5. 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 - how is that possible given crash reporting is landing now?
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`](https://developer.mozilla.org/en-US/docs/Web/API/Window/crashReport) and [`CrashReportContext`](https://developer.mozilla.org/en-US/docs/Web/API/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).

   Is that to be expected? 
2. Are the reporting endpoints supported, as documented in [`CrashReport`](https://developer.mozilla.org/en-US/docs/Web/API/CrashReport)

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

   ```http
   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
4. Is there a way to force a crash to test (in my [personal tests scripts](https://github.com/hamishwillee/various_webapi_tests/tree/main/ReportingAPI/crash) I tried allocating all resources etc, but Firefox is remarkably robust).
5. 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 - how is that possible given crash reporting is landing now?
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`](https://developer.mozilla.org/en-US/docs/Web/API/Window/crashReport) and [`CrashReportContext`](https://developer.mozilla.org/en-US/docs/Web/API/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`](https://developer.mozilla.org/en-US/docs/Web/API/CrashReport)

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

   ```http
   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](https://github.com/hamishwillee/various_webapi_tests/tree/main/ReportingAPI/crash) I tried allocating all resources etc, but Firefox is remarkably robust).

Back to Bug 2036160 Comment 4