Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

199
Views
Does the W3C Browser Reporting API (v1) also report unhandled javascript exceptions via the report type Crash?

I am keen seeing the relatively new W3C Reporting API (v1), even though browser support is still limited at the moment.

In the existing documentation ( web.dev, MDN ), it is mentioned that one type of report types is Crash (explanations for this type are: "The browser crashes while your site is open." / "Occurrence of crashes." / "Indicates that the website stopped running due to a browser crash.").

Based on the articles I found, I am wondering if the report type Crash also includes reports for unhandled javascript exceptions like the following code produces:

// undefinedVar is undefined
undefinedVar.toString()

(In the browser console, this code generates an error log like "Uncaught ReferenceError: undefinedVar is not defined".)

Are such unhandled javascript exceptions produced by a site also reported via the Reporting API using the Crash type or will such reports only generated for "real" browser crashes (=browser process crashed)?

about 4 years ago · Juan Pablo Isaza
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!