- From: Anne van Kesteren <annevk@opera.com>
- Date: Thu, 10 Mar 2011 16:10:58 +0100
- To: "Olli Pettay" <Olli.Pettay@helsinki.fi>, Olli@pettay.fi
- Cc: "www-dom@w3.org" <www-dom@w3.org>, "Jacob Rossi" <jrossi@microsoft.com>
On Thu, 10 Mar 2011 16:02:29 +0100, Olli Pettay <Olli.Pettay@helsinki.fi>
wrote:
> On 03/10/2011 10:01 AM, Anne van Kesteren wrote:
>> It is artificial because you can just invoke initEvent with the empty
>> string, false, and false, and the event object will be identical. So you
>> are essentially throwing for not invoking initEvent which is rather
>> silly.
>
> Why is that silly? Quite often when you have objects with
> some kind of init method, you want to "prevent" object usage
> before the init is called.
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.
--
Anne van Kesteren
http://annevankesteren.nl/
Received on Thursday, 10 March 2011 15:11:43 UTC