W3C home > Mailing lists > Public > public-webapi@w3.org > May 2006

Re: ISSUE-81: What should detail be for dblclick events?

From: Jonas Sicking <jonas@sicking.cc>
Date: Wed, 10 May 2006 12:53:05 -0700
Message-ID: <446244A1.2010808@sicking.cc>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Cc: Web APIs WG <public-webapi@w3.org>

Bjoern Hoehrmann wrote:

> * Jonas Sicking wrote:
> 
>>I can't think of any use cases where you'd want to be able to tell 
>>appart the first double-click (corresponding to clickEvent.detail == 2) 
>>and a second (corresponding to clickEvent.detail == 4).
>>
>>However, it seems easy enough to say that the detail should be the same 
>>as for the click event. This doesn't seem like a very harsh requirement 
>>on implementations since the information is already available. So why not?
> 
> We would first have to clearly require that this click event occurs (it
> does not at all in Internet Explorer and not consistently in Konqueror).
> I'm not sure why dblclick.detail == click.detail would be better than
> dblclick.detail == 2 or dblclick.detail == some undefined value though.

Giving it a constant, or undefined, value will provide absolutly no 
value at all to the web page. Making it equal to click.detail may 
provide some value to someone.

I do agree that we need to define if a click event is dispatched though, 
and if it's not then it might be harder to require dblclick.detail == 
click.detail. So we should decide on that first.

/ Jonas
Received on Wednesday, 10 May 2006 19:53:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:55 GMT