Marcel Weiher wrote:

> I suggest that the fix to double-click detection that was proposed
> on this list earlier should be implemented (and will try it myself
> now in order to see what happens):  send a #click: after the first
> mouseUp event, and make sure that the few existing #doubleClick:
> clients can deal with receiving a click before the double-click.

This is actually how a double click should always be designed. It should
always be signalled as a click event followed by a double click event, and
all uses of double click should be natural extensions of a single click.
E.g. single click selects object, double click performs most frequent action
on it.

Otherwise, e.g. nasty unpredictable things may happen if you miss the double
click threshold by a couple of milliseconds.

So my point was, I guess, go for it!

Henrik