-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.3.2
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
We have a new set of validity checks in our JavaScript interface code due to the switch from SpiderMonkey to V8, and a different routine for displaying JavaScript exceptions. The output should be made to match version 2.2 more closely than it currently does.
The display of the JavaScript code that threw an exception, along with a caret indicating where in the line the exception occurred, is not felt to be helpful.
SpiderMonkey:
> throw "There was a problem" Wed Jan 23 06:40:49.109 uncaught exception: There was a problem >
V8:
> throw "There was a problem" Wed Jan 23 06:41:11.570 javascript execution failed (shell):1 There was a problem throw "There was a problem" ^ >
- related to
-
SERVER-8926 Shell displays "JavaScript execution failed: " before all JavaScript errors, adds "L" before line number
- Closed