[Webkit-unassigned] [Bug 8519] WebCore doesn't fire window.onerror event when uncaught JavaScript exceptions are thrown

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Aug 16 14:15:56 PDT 2009


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


Erik Kay <erikkay at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |erikkay at chromium.org




--- Comment #28 from Erik Kay <erikkay at chromium.org>  2009-08-16 14:15:45 PDT ---
When you say "it can't be a compat concern", you're only looking at it from one
angle of compat.  I agree that it's unlikely that websites will break if this
callback doesn't exist.  However, the existence of the feature allows websites
to detect and fix other webkit compat issues more quickly.  For example, the
gmail case sited previously means that any unhandled exceptions can be logged
to a server where they can be detected, quantified, analyzed, etc.  Without
this, it's quite possible that the site owners won't realize that their site is
broken in webkit browsers as quickly as other browsers (or perhaps at all if
the effect of the error is subtle).

Incidentally, I ran into this myself trying to build some unit tests for chrome
extensions and not wanting to have to fill the code with zillions of try/catch
blocks.  The net effect for me is a lot more effort and a longer debug cycle
(since unhandled exceptions wind up leading to timeouts in the test rather than
hard errors).

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



More information about the webkit-unassigned mailing list