ISSUE-129: Revisit event constructors
event constructors
Revisit event constructors
- State:
- CLOSED
- Product:
- HISTORICAL: DOM3 Events [All Bugs and Issues use Bugzilla: http://tinyurl.com/Bugs-DOM3Events]
- Raised by:
- Doug Schepers
- Opened on:
- 2010-09-15
- Description:
- Simon Pieters <http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0125.html>:
[[
An idea for creating events is to support [Constructor] on all event
IDLs, which makes the createEvent method unnecessary.
Maybe we could even make the arguments to the constructor be called to
initFooEvent() directly, so instead of doing
var e = document.createEvent('MouseEvents');
e.initMouseEvent('click', ...);
foo.dispatchEvent(e);
you could do
foo.dispatchEvent(new MouseEvent('click', ...))
Another thing we could change is to make all but the first arguments to
initFooEvent() optional and let them have sensible defaults, so that if
all you care about is the event type, you can include just the first
argument.
If the constructor is called with no arguments, then initFooEvent() would
not be called.
]] - Related Actions Items:
- No related actions
- Related emails:
- Re: ISSUE-129 (event constructors): Revist event constructors [DOM3 Events] (from Jacob.Rossi@microsoft.com on 2011-08-12)
- Re: Conflicts between D3E and Web DOM Core (from annevk@opera.com on 2011-03-04)
- Conflicts between D3E and Web DOM Core (from jrossi@microsoft.com on 2011-03-03)
- ISSUE-129 (event constructors): Revist event constructors [DOM3 Events] (from sysbot+tracker@w3.org on 2010-09-15)
Related notes:
LAST CALL
Doug Schepers, 15 Sep 2010, 18:08:27This is a great V.Next feature request for the events model. However, at this stage in the evolution of DOM L3 Events, it's outside the scope of the spec. We should consider this in another/future specification (perhaps DOM Core?).
Jacob Rossi, 15 Apr 2011, 06:07:27Display change log
