New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Buggy piece selection in Firefox #5886
Comments
Can confirm this happening in Firefox on both Windows and Linux (doesn't happen in Chrome): |
Here is a FireFox performance profile on Linux, if it is of any help: |
I noticed that playing on firefox feels less smooth than on chrome, I can't exactly explain why however. This has changed recently, now also chrome feels less smooth, do you think that's the same issue you are describing here? |
Yes, playing on FireFox feels less smooth. It seems like FPS is lower and there are some lags with animation. Difficult to say whether Chrome feels less smooth for me now, can't tell the difference between now and before. FireFox still feels less smooth (hasn't changed for me). |
Hello, do you still face the same issue? If yes you could try the answer provided here: #7107 (comment) see if it changes anything |
In my case resistFingerprinting was disabled by default. Enabling it made the board events happen a bit more randomly (apparently reduceTimerPrecision has this effect when resistFingerprinting is enabled). |
How is it going almost 1 year later? |
I'm running Firefox 71.0 (64-bit) and the piece selection over the past month seems to be intermittently buggy.
Basically, I'll select a piece and either the mouse-click isn't being registered or its being registered but doesn't necessarily select the intended piece to move. I've had an increasing number of misclicks in high speed games as a result. An example for instance, as black moving Ngf6 rapidly has moved the f7 pawn to f6, and most people on the site are looking for a win instead of a good game (at least from my experience). Other examples include having doubled rooks ready for an exchange trade down and instead of the rook taking on c1 it moves a space to c6.
It only happens when there is a very rapid mouse movement and its intermittent. Its like the mouse cursor and coordinates being registered by the browser are out of sync for a small period of time and as a result the wrong move gets registered.
The text was updated successfully, but these errors were encountered: