W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2011

Re: ISSUE-147 (event re-dispatching): re-dispatching an event that already has its flow started [DOM3 Events]

From: Jacob Rossi <Jacob.Rossi@microsoft.com>
Date: Wed, 3 Aug 2011 17:14:42 +0000
To: "www-dom@w3.org" <www-dom@w3.org>, Sergey Ilinsky <sergey@ilinsky.com>
Message-ID: <D0BC8E77E79D9846B61A2432D1BA4EAE03406FFE@TK5EX14MBXC287.redmond.corp.microsoft.com>
Hi Sergey,

This behavior is already defined. If one calls dispatchEvent() with an event object already being dispatched, then a DISPATCH_REQUEST_ERR exception is thrown. [1]

Since this is already specified, no changes to the spec were made. Let us know if you have additional comments or concerns on this issue.

Thanks,

Jacob

[1] http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-EventTarget-dispatchEvent 

=============================================
From: Sergey Ilinsky <sergey@ilinsky.com>
Date: Fri, 24 Sep 2010 21:22:34 +0200
Message-ID: <AANLkTimUYmaAY012ZE-2HHUa=s06s_4X=7HU186OhXkS@mail.gmail.com>
To: www-dom@w3.org
I could not find details regarding if it is legal to call dispatchEvent
function with an event object that is already being propagated as its
argument.

Should this result into exception?

Sergey/
Received on Wednesday, 3 August 2011 17:15:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:08 GMT