Replying to [comment:3 dmethvin]:
Re comment #2, that is a bug and has already been filed/fixed for 1.5.2. I agree we're giving contradictory information, the example in http://api.jquery.com/bind/ does attach both handlers even though the text in http://api.jquery.com/dblclick/ warns about cross-browser issues. I do not think this is something worth normalizing, but if you would like to propose a solution (perhaps initially in a plugin) we could consider it.
Not sure to well understand what you mean when you "do not think this is sometingu worth normalizing".
May be I'm wrong but, from what I investigated, I seem that in the current state (no special survey), the risk of dysfunction when attaching both handlers is quite confirmed. So it will be worth to have a definitive solution to eliminate it, isn't it?
If yes, my only doubt is about the real efficacity of my own solution.
As a simple application developper, I'm obviously much less experienced than jQuery contributors. It is why I need your opinion: does it seem to you that my solution covers all aspects of the problem?
Particularly, apart from the simple timing issue, I investigated about the problem of different browsers receiving one or two clicks before firing dblclick (look at my updated test case http://jsfiddle.net/ky7xh/7/): seems that it doesn't matter.
But perhaps I'm blind to other aspects...
So once again your opinion should be very welcome.
Thanks in advance.