action #17960

JavaScript errors shouldn't be silently ignored

Added by mkittler almost 3 years ago. Updated over 1 year ago.

Status:NewStart date:24/03/2017
Priority:NormalDue date:
Assignee:-% Done:


Category:Feature requests
Target version:QA - future


Currently JavaScript errors in openQA are ignored and only visible when opening the development console in the web browser.

It would be useful if such errors would be

  1. visible to the user
  2. or logged on the server in case of failed API calls

instead of having no feedback at all.

In the second case the server could evaluate a referrer sent by the web UI to recognize failed API calls caused by the web UI specifically.


#1 Updated by coolo over 2 years ago

  • Target version set to future

showing javascript errors to the user sounds insane. Logging to the server sounds far from trivial though - gives quite some hints.

And logging the error without knowing the details of the user's setup sounds unhelpful too - and refering our users to external logging services sounds overkill. So I'm undecided if this is a good idea at all.

#2 Updated by okurz over 1 year ago

  • Target version changed from future to future

Also available in: Atom PDF