ISSUE-147: re-dispatching an event that already has its flow started
event re-dispatching
re-dispatching an event that already has its flow started
- State:
- CLOSED
- Product:
- HISTORICAL: DOM3 Events [All Bugs and Issues use Bugzilla: http://tinyurl.com/Bugs-DOM3Events]
- Raised by:
- Doug Schepers
- Opened on:
- 2010-10-06
- Description:
- Sergey Ilinsky in <http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0194.html>:
[[
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?
]] - Related Actions Items:
- No related actions
- Related emails:
- Re: ISSUE-147 (event re-dispatching): re-dispatching an event that already has its flow started [DOM3 Events] (from Jacob.Rossi@microsoft.com on 2011-08-03)
- Minutes, DOM3 Events telcon, 04 Feb 2011 (from schepers@w3.org on 2011-02-06)
- Minutes: DOM3 Events Telcon, 27 October 2010 (from schepers@w3.org on 2010-10-29)
- ISSUE-147 (event re-dispatching): re-dispatching an event that already has its flow started [DOM3 Events] (from sysbot+tracker@w3.org on 2010-10-06)
Related notes:
LAST CALL
Doug Schepers, 11 Oct 2010, 17:03:08This is defined in the spec via the DISPATCH_REQUEST_ERR exception: file:///C:/Users/jrossi/Documents/D3E/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-EventTarget-dispatchEvent
Jacob Rossi, 25 Apr 2011, 01:33:22Display change log
