Document Firefox Crash Reporting API Nightly support

[KirtiRamchandani]

Problem

Firefox 152 enables the Crash Reporting API in Nightly builds, but the MDN pages did not yet mention the Firefox preview and the CrashReport page pointed at a non-existent BCD key.

Root cause

The Gecko change enables dom.reporting.crash.enabled for Nightly builds. The CrashReport page should use the existing BCD key that represents delivery of crash reports through the Reporting-Endpoints default endpoint, while the new CrashReportContext/Window.crashReport support is tracked in a companion BCD update.

Solution

• Add Firefox 152 release notes for the Crash Reporting API Nightly preview.
• Add an Experimental features entry for dom.reporting.crash.enabled.
• Point the CrashReport page at http.headers.Reporting-Endpoints.default.receives_crash_type.

Tests

• npx --yes prettier@3.8.3 --config C:\Users\kirti\Documents\PRs\mdn-content\.prettierrc.json --check C:\Users\kirti\Documents\PRs\mdn-content\files\en-us\web\api\crashreport\index.md C:\Users\kirti\Documents\PRs\mdn-content\files\en-us\mozilla\firefox\releases\152\index.md C:\Users\kirti\Documents\PRs\mdn-content\files\en-us\mozilla\firefox\experimental_features\index.md
• npx --yes --package markdownlint-cli2@0.22.1 --package markdownlint-rule-search-replace@1.2.0 markdownlint-cli2 --config C:\Users\kirti\Documents\PRs\mdn-content\.markdownlint-cli2.jsonc C:\Users\kirti\Documents\PRs\mdn-content\files\en-us\web\api\crashreport\index.md C:\Users\kirti\Documents\PRs\mdn-content\files\en-us\mozilla\firefox\releases\152\index.md C:\Users\kirti\Documents\PRs\mdn-content\files\en-us\mozilla\firefox\experimental_features\index.md
• git diff --check

Related

Related docs work #44297
Companion BCD update: mdn/browser-compat-data#29782
Firefox bug: https://bugzil.la/2036160

[github-actions]

Preview URLs (3 pages)

• /en-US/docs/Mozilla/Firefox/Experimental_features
• /en-US/docs/Mozilla/Firefox/Releases/152
• /en-US/docs/Web/API/CrashReport

Flaws (1)

Note! 2 documents with no flaws that don't need to be listed. 🎉

Found an unexpected or unresolvable flaw? Please report it here.

URL: /en-US/docs/Mozilla/Firefox/Releases/152
Title: Firefox 152 release notes for developers (Beta)
Flaw count: 1

• macros:
  • Macro domxref produces link /en-US/docs/Web/API/SVGTextPathElement/side which doesn't resolve

External URLs (2)

URL: /en-US/docs/Mozilla/Firefox/Experimental_features
Title: Experimental features in Firefox

• https://bugzil.la/2036160 (1 time) (Note! This may be a new URL 👀)

---

URL: /en-US/docs/Mozilla/Firefox/Releases/152
Title: Firefox 152 release notes for developers (Beta)

• https://bugzil.la/2036160 (1 time) (Note! This may be a new URL 👀)

(comment last updated: 2026-06-02 05:47:01)

[hamishwillee]

Thanks!!!

[hamishwillee]

Can you make an update like this and prettier. Nightly means it is in all releases, but only enabled by default in nightly.

Suggested change

	| Developer Edition | - | - |
	| Beta | - | - |
	| Release | - | - |
	| Developer Edition | 152 | No |
	| Beta | 152 | No |
	| Release | 152 | No |

[hamishwillee]

Please move up just below the API heading above. We use last-added ordering within a sub heading.

[hamishwillee]

Suggested change

	It exposes the {{domxref("Window.crashReport")}} property and the {{domxref("CrashReportContext")}} interface, which stores key-value data for the current top-level browsing context.
	It exposes the {{domxref("Window.crashReport")}} property and the {{domxref("CrashReportContext")}} interface, which store key-value data for the current top-level browsing context.

[hamishwillee]

We indicate nightly like this.

Suggested change

	- **Crash Reporting API**: `dom.reporting.crash.enabled`
	The [Crash Reporting API](/en-US/docs/Web/API/CrashReport) is now available in Nightly builds, where it is enabled by default.
	This exposes {{domxref("Window.crashReport")}} and {{domxref("CrashReportContext")}}, allowing pages to store key-value diagnostic data that can be included in {{domxref("CrashReport")}} objects sent through the [Reporting API](/en-US/docs/Web/API/Reporting_API).
	([Firefox bug 2036160](https://bugzil.la/2036160)).
	- **Crash Reporting API** (Nightly): `dom.reporting.crash.enabled`
	The [Crash Reporting API](/en-US/docs/Web/API/CrashReport) is now supported.
	This exposes {{domxref("Window.crashReport")}} and {{domxref("CrashReportContext")}}, allowing pages to store key-value diagnostic data that can be included in {{domxref("CrashReport")}} objects sent through the [Reporting API](/en-US/docs/Web/API/Reporting_API).
	([Firefox bug 2036160](https://bugzil.la/2036160)).

[hamishwillee]

@KirtiRamchandani Thanks! What made you decide to look at this issue?
These project issues are generally handled by the MDN team. I'm happy to take the fix because it is not far off what I would have done, but it isn't the best use of either of our efforts.
Usually best to start with issues labelled "good first issue".

Either way, we should hold off merging this just until this is answered https://bugzilla.mozilla.org/show_bug.cgi?id=2036160#c4 - i.e. there is something going on with the exposed interfaces.

[KirtiRamchandani]

Thanks for the review. I pushed 8a2bcc9 with the requested ordering, table values, and Nightly wording. Prettier and markdownlint pass for the touched files.

I picked this up because it was a current Firefox 152/dev-doc-needed docs issue and looked scoped to release notes/experimental features. Understood that project issues are usually MDN-owned; I’ll focus on good-first or explicitly contributor-friendly issues going forward.

For the exposed-interface and endpoint details, I agree with holding merge until https://bugzilla.mozilla.org/show_bug.cgi?id=2036160#c4 is answered. I don’t want to infer runtime exposure from the pref/IDL alone.