← back to v139 · crash-reporting-api-specify-crash-reporting-to-receive-only-crash-reports
conformance · v139
v139 · crash-reporting-api-specify-crash-reporting-to-receive-only-crash-reports — conformance probe
6 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
reporting-observer-exposed |
ReportingObserver is exposed; subscribers can observe a 'crash' report type filtered to the crash-reporting endpoint. spec ↗ | exists | … | |
report-interface-exposed |
Report interface is exposed; crash reports surface as Report objects with type and body fields. | script | … | |
reporting-observer-accepts-crash-type |
ReportingObserver can be instantiated with types: ['crash'] without throwing, which is how authors filter to crash-only. spec ↗ | script | … | |
reporting-observer-take-records |
ReportingObserver.prototype.takeRecords exists and lets consumers drain currently-buffered records (including crash reports). | typeof | … | |
reporting-observer-observe-method |
ReportingObserver.prototype.observe is exposed; calling it activates the buffered crash report stream. | typeof | … | |
fetch-supports-reporting-endpoints-header |
fetch() is available so the browser can post crash payloads to the Reporting-Endpoints-declared endpoint named 'crash-reporting'. | typeof | … |