You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chrome recently landed an awesome new feature where an actual error object is passed to window.onerror. Without an actual error object, it is really difficult make use of the window.onerror because the original context is lost and no stack trace is available. Even libraries like stacktrace.js are unable to work around this.
Any idea if zone.js is able to work around this for IE and FF?
Chrome recently landed an awesome new feature where an actual error object is passed to
window.onerror
. Without an actual error object, it is really difficult make use of thewindow.onerror
because the original context is lost and no stack trace is available. Even libraries like stacktrace.js are unable to work around this.Any idea if zone.js is able to work around this for IE and FF?
References:
https://code.google.com/p/chromium/issues/detail?id=147127
https://bugzilla.mozilla.org/show_bug.cgi?id=355430
stacktracejs/stacktrace.js#26
The text was updated successfully, but these errors were encountered: