Voting button uncertainty #1987
Description
On a very slow connection, or when the server is very slow, clicking on a voting button to vote up or down has no visible effect, then the change happens later, when the server response arrives. This means that clicking twice will result in the vote being cancelled. It will appear to have worked when the first server response arrives, but later when the second server response arrives it will be cancelled.
This extends to multiple clicks. Clicking an even number of times will result in no net change, while clicking an odd number of times will result in the same change as clicking once. In either case the voting button will keeping changing as the server responses arrive.
This could leave a user thinking that they know what the outcome is, but then it changes after they stop looking or change tab or visit another page.
Is there a way to change this behaviour without preventing the user from reversing an accidental vote?
Would it be better for the button to change immediately to reflect the change that has been requested from the server, so the user doesn't think it has failed and doesn't try again? This would still allow a user to click again to remove a vote that they cast accidentally, and that removal would also appear immediately.