W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2008

[whatwg] window.onerror -ancient feature needs upgrade

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 25 Nov 2008 06:16:04 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0811250610330.17414@hixie.dreamhostps.com>
On Tue, 19 Aug 2008, Garrett Smith wrote:
> On Tue, Aug 19, 2008 at 6:16 PM, Ian Hickson <ian at hixie.ch> wrote:
> > On Sat, 22 Sep 2007, Garrett Smith wrote:
> >>
> >> window.onerror
> >>
> >> There needs to be a way to capture errors on the window.
> >
> > Is window.onerror not enough?
> 
> window.onerror would be sufficient if it:
>   * accepted an Error parameter.
>   * fired when an EventListener callback had an Error
>   * fired when a callback in setTimeout had an Error
> 
> But unfortunately, none of the above is true. At least some of it is 
> true in some browsers.

HTML5 now requires the second and third of those. It doesn't do the first.


> Accepting an Error parameter is important because it provides standard 
> information of the Error or Exception. At least one implementation 
> provides a 'stack' property (Firefox). Another implementation provides 
> stack info in the error message (Opera).

I agree that it would be nice but I think we should punt this until the 
next version.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 24 November 2008 22:16:04 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:07 UTC