🐛 benchmark 04_select1k failed: difference between mousedown and click is unusually long

[MattParkerDev]

🐛 benchmark 04_select1k failed: difference between mousedown and click is unusually long

[krausest]

Oh, that was me... I added a check yesterday due to #1442.
The duration I chose was long enough to prevent such an error on my macbook, but as it seems it was too low.
I commented out throwing the error. (9b73d69) You could try to update, recompile via npm run compile in webdriver-ts and run again.
It would be nice if you could report here the maximum value for the "difference between mousedown and click is unusually long" message in the log file.

[Niedzwiedzw]

@krausest couldn't you just start counting from mousedown? that would be most fair

[krausest]

We could measure from mousedown (but wouldn't be mouseup then be a better choice?)
But there's a random(?) delay for some frameworks like in this case:

There's a delay of more than 3 msecs between mousedown and click. I don't know where this comes from.
I think it wouldn't help us getting better results if we added this delay. Nevertheless it should be considered cheating if someone put his logic in a mousedown handler.