Is this a docs error? It describes exactly what you do:

"The sequence of events triggered varies from browser to browser, with some receiving two click events and others only one."

Unless you are saying that it is *also* worth mentioning one could use a timeout based approach? Is that what you're getting at?

No, I am saying this is perfectly valid and true:

It is inadvisable to bind handlers to both the click and dblclick events for the same element. The sequence of events triggered varies from browser to browser, with some receiving two click events and others only one.

but this:

the dblclick event should be simulated within the click handler.

obviously can't work in a browser that only fires a single click.

obviously can't work in a browser that only fires a single click.

Sure it can, using the timer trick mentioned in the documentation. That's basically what either the browser or underlying operating system is doing to detect double clicks. I think the docs are okay as-is, but if you have some suggestions on rewording let us know.

It's a really bad idea to use double clicks in a web interface, it's not something that most people expect.

Unless I am missing something and just being an idiot (quite possible), if I only have a click handler, and the browser fires a click and then a dblclick, checking the time between click will do no good, as the second click will be ignored because I have nothing bound to dblclick. ''The second click event is not fired even if no event is bound to dblclick.''

If instead I have something bound to click that does the time checking, and something bound to dblclick for the browsers that use only it, I will be double firing my dblclick in browsers that give me two clicks and a dblclick.

It's a really bad idea to use double clicks in a web interface, it's not something that most people expect.

I totally agree with that, however, if the docs propose a possible solution, I feel it should work, or not be provided.

I think the docs would be better if they did one of the following:

1. Just stated the problem

It is inadvisable to bind handlers to both the click and dblclick events for the same element. The sequence of events triggered varies from browser to browser, with some receiving two click events and others only one.

2. State the problem and give some advice on how to fix it, but not make it sound like a complete solution if it is not.

It is inadvisable to bind handlers to both the click and dblclick events for the same element. The sequence of events triggered varies from browser to browser, with some receiving two click and one dblclick event and others only a single click and dblclick event. You can get around this by checking the time between click/dblclick events, and manually firing your event when appropriate.

3. Providing a solid method to make it work. I do not have a good example for how to do this. I am sure it can be done, but I was more interested in making it work for my case than coming up with the perfect solution.

If you still disagree with me, please close this ticket and I will not bring it up again.

Ah, okay, I see what you are saying. The docs wording is ambiguous. I think it essentially means "making an element respond to both click and double-click is not a good idea. But you forge ahead and do it anyway, the solution may involve attaching both a click and double-click handler so it can work on all browsers." Does that sound right?

I think it may be best to remove any prescriptive attempt at a solution here, so that's what I've done. There is a user comment on the page that includes a link with code, in case anyone wants to do it.

Thank you, I very much like the "vary by operating system and browser, and is often user-configurable." as that has been on my mind a lot recently.