[Webkit-unassigned] [Bug 55092] Stack information of uncaught Error object should be available in window.onerror

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=55092


Timothy Quinn <tim.c.quinn at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tim.c.quinn at gmail.com




--- Comment #3 from Timothy Quinn <tim.c.quinn at gmail.com>  2011-08-11 14:12:04 PST ---
(In reply to comment #2)
I agree with the essence of the bug in that the window.onerror simply does not provide the functionality required for inline debugging. Its about as useful as IE's "Object not defined" ubiquitous error.

I strongly suggest further discussion of this to try and nail down a solution to make window.onerror more useful in WebKit.

In FireFox, we get an error object and thus we can read the error.stack and parse the result. It's not pretty, but it works as I have a full stack of source file names and line numbers which is 95% of what I need. Personally, this is my preferred

IE supports the call stack crawling and this has some nice features like being able to inspect the arguments of each level within the call stack. This methodology does not contain the source file names or line numbers which in its one kind of sucks.

If we can get both methods that would be absolutely awesome :)

PLEASE don't kill this request off or at least help us get to a solution that brings final closer to this fundamental gap in WebKit. I've been waiting for years for this fix and would love to get my libraries ported over to WebKit but for now, I just cannot support WebKit because it lacks a decent master error handler.

- TCQ

BTW I really do care about error handlers. I'm the dude who drove critical fix for Mozilla 1.3 which brought it up to par for better debugging: https://bugzilla.mozilla.org/show_bug.cgi?id=158592

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.