W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2010

Re: ISSUE-144 (propagation exceptions): exceptions in handlers during event propagation [DOM3 Events]

From: Garrett Smith <dhtmlkitchen@gmail.com>
Date: Wed, 6 Oct 2010 11:52:11 -0700
Message-ID: <AANLkTi=Ho0WwHwN9A8QoCjJ5Wbtv2tmRpsPr0ZsuP+Ca@mail.gmail.com>
To: Web Applications Working Group WG <public-webapps@w3.org>
On 10/5/10, Web Applications Working Group Issue Tracker
<sysbot+tracker@w3.org> wrote:
>
> ISSUE-144 (propagation exceptions): exceptions in handlers during event
> propagation [DOM3 Events]
>
> http://www.w3.org/2008/webapps/track/issues/144
>
> Raised by: Doug Schepers
> On product: DOM3 Events
>
> Sergey Ilinsky in
> <http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0191.html>:
> [[
> How do execution exceptions occurred in handlers during the event
> propagation affect the event flow?
> Should the event propagation be stopped, should it continue?
> Is this specified?
> ]]
>

Event propagation must continue as specified in DOM 2 Events, which
clearly explains that all registered EventListeners of any EventTarget
are guaranteed to be triggered by any event which is received by that
EventTarget.

Section 1.2.1. "basic event flow" goes on to explicitly state:
"Any exceptions thrown inside an EventListener will not stop
propagation of the event. It will continue processing any additional
EventListener in the described manner."

An event propagation must continue. One callback firing an error does
not get to stop that.

Garrett
Received on Wednesday, 6 October 2010 19:50:05 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:41 GMT