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: Ms2ger <ms2ger@gmail.com>
Date: Fri, 13 May 2011 23:09:45 +0200
Message-ID: <4DCD9E19.9030205@gmail.com>
To: www-dom@w3.org
On 05/10/2011 08:00 PM, Glenn Maynard wrote:
> On Tue, May 10, 2011 at 5:57 AM, Jonas Sicking<jonas@sicking.cc>  wrote:
>
>> On Tue, May 10, 2011 at 2:19 AM, Simon Pieters<simonp@opera.com>  wrote:
>>> On Tue, 10 May 2011 09:53:36 +0200, Jonas Sicking<jonas@sicking.cc>
>> wrote:
>>> 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
>>
>> Why? What was the advantage with that approach? I'd rather not head
>> down a path that'll make us add extra API just to check the
>> initialized flag if someone comes up with a use case a couple of years
>> down the road.
>>
>
> I don't think this was a good change, either, as I said at the time: adding
> extra state is worse than all of the other options (such as using an empty
> event type to mean "not initialized").  I figured it would make more sense
> to shelve the DOM Core-related discussions until Anne returns, though.
>

AFAICT, both Gecko and Presto seem to match the specification, while 
WebKit doesn't. (I haven't tested Trident.) If you convince UAs to 
implement the behaviour you prefer, I'll be happy to update DOM Core 
accordingly. Otherwise, I haven't seen any new information in this thread.

Thanks
Ms2ger
Received on Friday, 13 May 2011 21:10:18 GMT

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