W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2013

[whatwg] Stack trace in window.onerror

From: Ian Hickson <ian@hixie.ch>
Date: Fri, 12 Jul 2013 17:17:35 +0000 (UTC)
To: Nathan Broadbent <nathan.f77@gmail.com>, Garrett Smith <dhtmlkitchen@gmail.com>, Oliver Hunt <oliver@apple.com>, Elliott Sprehn <esprehn@chromium.org>
Message-ID: <alpine.DEB.2.00.1307121715430.15729@ps20323.dreamhostps.com>
Cc: whatwg@lists.whatwg.org
On Tue, 5 Feb 2013, Nathan Broadbent wrote:
> 
> 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?

This seems useful, but I don't think it's specific to window.onerror. I 
would recommend approaching the es-discuss list about this.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 12 July 2013 17:17:59 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:03 UTC