[Webkit-unassigned] [Bug 64150] New: dispatchEvent should raise an exception if the event object is already being dispatched

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=64150

           Summary: dispatchEvent should raise an exception if the event
                    object is already being dispatched
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Event Handling
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: dominicc at chromium.org


This came up in the context of bug 63934.

DOM Events says calling dispatchEvent with an event that is being dispatched should raise DISPATCH_REQUEST_ERR.
<http://www.w3.org/TR/2011/WD-DOM-Level-3-Events-20110531/#events-EventTarget-dispatchEven

For context, the status quo in WebKit is that calling dispatchEvent and passing an event that is in the process of being dispatched resets the event’s target. Subsequent event listeners of the original event dispatch see an unrelated event.target, despite event.target being a readonly attribute that DOM Events says "must be the EventTarget object on which dispatchEvent is called." Firefox 5.0 makes dispatchEvent of an event that is being dispatched a no-op.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.