- From: Glenn Maynard <glenn@zewt.org>
- Date: Fri, 11 Mar 2011 15:39:53 -0500
- To: Jacob Rossi <jrossi@microsoft.com>
- Cc: Anne van Kesteren <annevk@opera.com>, Olli Pettay <Olli.Pettay@helsinki.fi>, "Olli@pettay.fi" <Olli@pettay.fi>, "www-dom@w3.org" <www-dom@w3.org>
On Fri, Mar 11, 2011 at 12:54 PM, Jacob Rossi <jrossi@microsoft.com> wrote: > Actually, null string has nothing to do with it. Anne has spec'd the default to be empty string, not null. The null string and the empty string mean the same thing: "", not null. > But spending time defining behavior that conflicts all current implementations and has no use case just stalls the progression of DOM L3 Events and yields no real value add. Not all. WebKit doesn't check whether initEvent was called; it just checks whether event.type != "". If it's to allow e.type == "", it would need a new flag indicating whether initEvent was called. Firefox seems buggy here. It neither dispatches the event nor throws an exception when dispatchEvent is called without initEvent. It seems to silently do nothing, which I think is wrong in any case. (I havn't checked the source to see precisely what's happening.) -- Glenn Maynard
Received on Friday, 11 March 2011 20:40:25 UTC