← back to v137 · call-stacks-in-crash-reports-from-unresponsive-web-pages
conformance · v137
v137 · call-stacks-in-crash-reports-from-unresponsive-web-pages — 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 |
|---|---|---|---|---|
reportingobserver-exists |
Reporting API exposes ReportingObserver, the umbrella mechanism crash reports plug into (even though crash reports themselves are delivered out-of-band). spec ↗ | exists | … | |
reportingobserver-is-constructor |
ReportingObserver is constructable with a callback. spec ↗ | typeof | … | |
report-interface-exists |
The Report interface wraps each delivered report body and exposes type/url/body. spec ↗ | script | … | |
document-policy-header-recognised |
Documents opt in to stack collection via the include-js-call-stacks-in-crash-reports document policy directive (header parsed at navigation time). spec ↗ | script | … | |
report-type-crash-is-string |
The crash report type identifier is the string 'crash'. spec ↗ | script | … | |
crash-report-body-shape-known |
CrashReportBody is a dictionary with reason ('oom' | 'unresponsive') and optional stack fields per the spec. spec ↗ | script | … |