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

[bugzilla-daemon at webkit.org]

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





--- Comment #35 from kangax <kangax at gmail.com>  2009-09-12 15:44:38 PDT ---
(In reply to comment #34)
> > Agreed. Another good example of this is that window.onerror is called if there
> > is a syntax error on the page, which try/catch can not catch.
> 
> Which errors? 

Errors that I could not anticipate.

> 
> Whatever errors you have, they should have been prevented before the release

Isn't that like saying that whatever bugs in the system you have they should
have been prevented before the release? Unfortunately, that's not how things
work :)

> and this comes back to proper testing.

What is proper testing? I do have a test suite which I always keep "green".
Yet, there are things I simply can't test or can't predict upfront. There could
be errors due to unexpected user input. I do try to tame such input, but it
still creeps in and being able to catch such errors later rather than never
seems like a good idea to me.

Then there are unknown environments that I simply can't physically test. I
don't have a Playstation 3 so I don't know how NetFront engine will react to my
javascript (even though I try to design defensively). I can't test Opera 9.25
since (for whatever reason) it doesn't start on my Mac OS X. It is only after
seeing these errors logged through `window.onerror` that I can "fix" them (and
change test suite appropriately).

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