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: Mon, 29 Oct 2012 22:09:30 +0000
To: public-script-coord@w3.org
Message-ID: <bug-17713-3890-NqlPQJE0Zi@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17713

--- Comment #9 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
Surely most callbacks aren't affected; in most cases if a callback raises an
exception you just want to keep propagating it, no? Maybe I don't follow what
you mean exactly? I agree that other callbacks need to define some of this too,
but I don't see why that changes the resolution here.

Whether DOM (or WebIDL) uses a hook that HTML then defines (as for mutation
observers in DOM Core or global environment scopes in WebIDL) or calls into
HTML directly (as XHR does) is a non-issue to me, this can be defined either
way. (But I don't really understand why we're avoiding dependencies so much.
The truth is this is just one platform.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 29 October 2012 22:09:31 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:07 UTC