Open GoogleCodeExporter opened 9 years ago
I agree on the premise -- it's undesirable to log an exception inside the
logger,
just as it is to debug a debugger. One point to make is that if Blackbird owns
and
suppresses the window.onerror, it would be impossible for any other library
(such as
DamnIT [site: http://damnit.jupiterit.com/] -- designed for the sole purpose of
sending an xhr to the owner of the site) to function.
-gc
Original comment by GeorgeC...@gmail.com
on 18 Oct 2008 at 7:39
@GeorgeCalm
> it would be impossible for any other library (such as
> DamnIT [site: http://damnit.jupiterit.com/] -- designed
> for the sole purpose of sending an xhr to the owner of
> the site) to function.
How about wrapping window.onerror much like the functions that wrap
window.onload? Here is a perfect
example of what I mean:
http://simonwillison.net/2004/May/26/addLoadEvent/
Original comment by joepec...@gmail.com
on 1 Nov 2008 at 1:45
Good point, Joe. Wrapping the window.onerror does allow multiple libraries to
catch
the error. It would affect the entire page, not just blackbird, and would
prevent any
code running after the error is caught in window.onerror to execute. Why not go
with
try/catch?
Original comment by GeorgeC...@gmail.com
on 1 Nov 2008 at 7:49
Original issue reported on code.google.com by
joern.h...@gmail.com
on 10 Oct 2008 at 5:01