Double-click not fast enough in Chrome mode to be registered as double-click

[kensoh]

Raising this issue on behalf of user email so that other users can benefit -

---

We have some issues with the double click function - we have an internal application that uses this double click function but for some reason that it doesn’t work – we suspect that the application is not recognising the TagUI’s double click due to the time lag from 1st to 2nd click.

We tested it on other website (http://unixpapa.com/js/testmouse.html) to test the double click. It does not recognize the double click as double click. Instead, it recognized it as 2 individual fast clicks.

Is there a way to make the double click’s time lag (from 1st to 2nd click) faster?

[kensoh]

Trying to shorten the polling time to Chrome from 100ms to 10ms (10 times faster) does not make the click work fast enough for click -> release -> click -> release to be registered as double-click on the above website.

Chrome standard automation protocol doesn't have a provision for double-click. Alternative way is to do a click x 2 -> release x 2. Though logically this sounds incorrect, it seems to be the only way to initiate this and above commit works for above mouse-click testing website.

This feature is now usable from cutting edge version.