d6ae874038
Chromium added the actual `error` object to the 5th parameter in `window.onerror`. This should be emitted as opposed to the `errorMsg` string. Worse yet, since `errorMsg` wasn't an instance of `Error`, any code that assumes this in any `process.on('uncaughtException')` handler would fail. Also, correctly emitting the error provides the stack trace.
This is now an HTML5 standard.
Sources:
- https://html.spec.whatwg.org/multipage/webappapis.html#errorevent
- https://mikewest.org/2013/08/debugging-runtime-errors-with-window-onerror
- https://code.google.com/p/chromium/issues/detail?id=147127
|
||
|---|---|---|
| .. | ||
| api | ||
| lib | ||
| resources/mac | ||
| atom_render_view_observer.cc | ||
| atom_render_view_observer.h | ||
| atom_renderer_client.cc | ||
| atom_renderer_client.h | ||
| guest_view_container.cc | ||
| guest_view_container.h | ||