Bug 64913
| Summary: | dispatchEvent should raise INVALID_STATE_ERR, not DISPATCH_REQUEST_ERR, if its argument is being dispatched | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Dominic Cooney <dominicc> |
| Component: | UI Events | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | annevk, ap, dominicc |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#dom-eventtarget-dispatchevent | ||
Dominic Cooney
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>
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Dominic Cooney
Actually, this may be controversial:
<http://lists.w3.org/Archives/Public/www-dom/2011JulSep/thread.html#msg42>