I compared the timings of touchstart, touchend and click as well as double click between Firefox and Chrome. From that it shows that Chrome is indeed less strict of that triggers a double click. The test page is also accessible [here](https://denvercoder21.github.io/firefox-debugging/bugs/1798141.html). The following timings _**did not**_ trigger a double click in Firefox (too slow): ```` ∆ Start-End: 110 ms ∆ Start-Start: 228 ms ∆ End-Start: 117 ms ```` The following timings _**did**_ trigger a double click in Chrome: ```` ∆ Start-End: 140 ms ∆ Start-Start: 412 ms ∆ End-Start: 269 ms ```` It would have been interesting when the single finger tap timer times out on Chrome and if that ends up creating a click event. But inspecting this collides with long tap being triggered, and so far I couldn't find a way to disable that in Chrome.
Bug 1798141 Comment 25 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I compared the timings of touchstart, touchend and click as well as double click between Firefox and Chrome. From that it shows that Chrome is indeed less strict with timings that trigger a double click. The test page is also accessible [here](https://denvercoder21.github.io/firefox-debugging/bugs/1798141.html). The following timings _**did not**_ trigger a double click in Firefox (too slow): ```` ∆ Start-End: 110 ms ∆ Start-Start: 228 ms ∆ End-Start: 117 ms ```` The following timings _**did**_ trigger a double click in Chrome: ```` ∆ Start-End: 140 ms ∆ Start-Start: 412 ms ∆ End-Start: 269 ms ```` It would have been interesting when the single finger tap timer times out on Chrome and if that ends up creating a click event. But inspecting this collides with long tap being triggered, and so far I couldn't find a way to disable that in Chrome.
I compared the timings of touchstart, touchend and click as well as double click between Firefox and Chrome. From that it shows that Chrome is indeed less strict with timings that trigger a double click. The test page is also accessible [here](https://denvercoder21.github.io/firefox-debugging/bugs/1798141.html). The following timings _**did not**_ trigger a double click in Firefox (too slow): ```` ∆ Start/End: 110 ms ∆ Start/Start: 228 ms ∆ End/Start: 117 ms ```` The following timings _**did**_ trigger a double click in Chrome: ```` ∆ Start/End: 140 ms ∆ Start/Start: 412 ms ∆ End/Start: 269 ms ```` It would have been interesting when the single finger tap timer times out on Chrome and if that ends up creating a click event. But inspecting this collides with long tap being triggered, and so far I couldn't find a way to disable that in Chrome.