Bug 64913 - dispatchEvent should raise INVALID_STATE_ERR, not DISPATCH_REQUEST_ERR, if its argument is being dispatched
Summary: dispatchEvent should raise INVALID_STATE_ERR, not DISPATCH_REQUEST_ERR, if it...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: UI Events (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL: http://dvcs.w3.org/hg/domcore/raw-fil...
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-20 17:49 PDT by Dominic Cooney
Modified: 2011-07-31 21:54 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dominic Cooney 2011-07-20 17:49:47 PDT 
Bug 64150 made dispatchEvent raise DISPATCH_REQUEST_ERR if its argument is already being dispatched, per the DOM 3 Events spec:

<http://www.w3.org/TR/2011/WD-DOM-Level-3-Events-20110531/#events-EventTarget-dispatchEvent>

Raising an exception is right, however DOM Core specifies that it should raise INVALID_STATE_ERR:

<http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#dom-eventtarget-dispatchevent>
Comment 1 Dominic Cooney 2011-07-31 21:54:42 PDT 
Actually, this may be controversial:

<http://lists.w3.org/Archives/Public/www-dom/2011JulSep/thread.html#msg42>