- From: Glenn Maynard <glenn@zewt.org>
- Date: Thu, 10 Mar 2011 10:45:08 -0500
- To: Anne van Kesteren <annevk@opera.com>
- Cc: Olli Pettay <Olli.Pettay@helsinki.fi>, Olli@pettay.fi, "www-dom@w3.org" <www-dom@w3.org>, Jacob Rossi <jrossi@microsoft.com>
On Thu, Mar 10, 2011 at 10:10 AM, Anne van Kesteren <annevk@opera.com> wrote:
> Because the initEvent() method in this case does not necessarily have to
> change anything. When invoked it could leave the object completely
> unchanged. Having it unset some special flag ("initEvent() invoked") would
> serve no purpose.
FWIW, the requirement to call initEvent seemed directly tied in with
the requirement to have a non-empty event type. DOM Events requires
the latter, so there's no additional restriction imposed by requiring
initEvent--it's implied anyway--and it doesn't introduce additional
state, since checking for an empty event type implicitly checks
whether initEvent was called.
Since DOM Core does allow the null string as an event type (consistent
with most browsers), it makes sense for the initEvent requirement can
go away with it. At that point, it's just pointless additional state.
--
Glenn Maynard
Received on Thursday, 10 March 2011 15:45:42 UTC