- From: Rick Waldron <waldron.rick@gmail.com>
- Date: Fri, 12 Jul 2013 18:02:29 -0400
- To: Garrett Smith <dhtmlkitchen@gmail.com>
- Cc: Elliott Sprehn <esprehn@chromium.org>, "whatwg@lists.whatwg.org" <whatwg@lists.whatwg.org>, Oliver Hunt <oliver@apple.com>, Nathan Broadbent <nathan.f77@gmail.com>, Ian Hickson <ian@hixie.ch>
On Fri, Jul 12, 2013 at 5:51 PM, Garrett Smith <dhtmlkitchen@gmail.com>wrote: > On 7/12/13, James Greene <james.m.greene@gmail.com> wrote: > > Ian — > > Hi James - > > I've interleaved, combined with your top post below. > > > I'm curious: would do you say that? All evergreen browsers already > include > > a `stack` property on their core `Error` prototypes, so it seems to me > that > > the only thing preventing us from getting that useful information for > > unhandled errors is the fact that `window.onerror` does not provide us > with > > a real Error object instances (or even fake ones with shell properties in > > the case of cross-domain errors). > > > > If I'm mistaken, please clarify. Thanks! > > > That's my understanding. This issue has come up a number of times, > for at least 10 years, so I'm surprised at Ian's answer as well. > > Thread: "Add window.getLastError (or modify invocation arguments of > window.onerror)" > whatwg.org/2013-February/038848.html > > > Problem regarding getting the Error from window.onerror. > > >> > The current information passed to window.onerror rarely provides > >> > sufficient information to find the cause of the error. The column > >> > number > >> > argument will be a big step forward, but a stack trace would be > >> > especially useful. I would like to add my support for improving the > >> > window.onerror arguments, with a fifth argument for stack trace. Is > >> > there anything that James or I could do to move this discussion along? > >> > > Ian's reply: > >> This seems useful, but I don't think it's specific to window.onerror. I > >> would recommend approaching the es-discuss list about this. > >> > Is there a proposal on es-discuss that addresses this "global error > stack" situation? > To clarify, the only involvement TC39/es-discuss has with the specification of Error stack traces is here: http://wiki.ecmascript.org/doku.php?id=strawman:error_stack . window.onerror out of scope for ES. Rick
Received on Friday, 12 July 2013 22:03:14 UTC