W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2012

[Bug 17713] Exceptions thrown from event handlers should not be propagated

From: <bugzilla@jessica.w3.org>
Date: Tue, 27 Nov 2012 07:30:19 +0000
To: public-script-coord@w3.org
Message-ID: <bug-17713-3890-U7JAk3hp9u@http.www.w3.org/Bugs/Public/>

Boris Zbarsky <bzbarsky@mit.edu> changed:

           What    |Removed                     |Added
                 CC|                            |bzbarsky@mit.edu

--- Comment #10 from Boris Zbarsky <bzbarsky@mit.edu> ---
This really depends on what we mean by "propagated".

Should calling a callback not report an exception to error consoles and
window.onerror if the caller is itself called from some code that has a
try/catch?  I would argue that it _should_ in fact do so regardless of what's
going on with try/catch....  The alternative is that people start getting very
confused as to why their exceptions are not being reported.  We've run into
this with Gecko a good bit, since we do have that exception-swallowing behavior
in a bunch of cases.

Our (Gecko's) current implementation of WebIDL callbacks reports exceptions on
return from the callback, and I have no plans to change that, honestly.

You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 27 November 2012 07:30:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:07 UTC