W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2011

Re: WebApps-ISSUE-178 (empty string and null event types): Implementations and DOM Core allow empty string and null event types [DOM3 Events]

From: Simon Pieters <simonp@opera.com>
Date: Tue, 10 May 2011 11:19:21 +0200
To: "Jacob Rossi" <Jacob.Rossi@microsoft.com>, "Jonas Sicking" <jonas@sicking.cc>
Cc: "www-dom@w3.org" <www-dom@w3.org>, "annevk@opera.com" <annevk@opera.com>
Message-ID: <op.vu9dijpyidj3kv@simon-pieterss-macbook.local>
On Tue, 10 May 2011 09:53:36 +0200, Jonas Sicking <jonas@sicking.cc> wrote:

> On Monday, May 9, 2011, Jacob Rossi <Jacob.Rossi@microsoft.com> wrote:
>> Hi folks,
>>
>> In recognition that implementations support null and empty string event  
>> types and that DOM Core allows this, we accepted the change to D3E to  
>> remove this restriction. I have removed the spec text in the exceptions  
>> section which required
>>  an exception be thrown in these cases.
>
> Hmm. I only vaguely remember the tail end of this discussion, but
> wasn't the conclusion that it was better to let empty string signify
> an uninitialized event? Thus making empty string a not allowed name.
>
> The alternative is to force the event to hold some hidden state which
> indicates if it has been initialized or not. This is worse both from
> an implementation complexity aspect, as well as removes the ability
> for pages to check if an event has been initialized (I don't have any
> use cases for the latter, but it's a nice free bonus)

Some argued for that but DOM Core was then changed to have a flag -  
http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#initialized-flag

-- 
Simon Pieters
Opera Software
Received on Tuesday, 10 May 2011 09:19:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:07 GMT