A player in my group chat sent a screen recording last week that took three viewings to follow. He was flicking a leaderboard with his thumb, overshot the first row, and the whole page blinked and came back to its loading screen. No error, no reconnect banner. The round simply stopped existing, and the page looked healthy afterwards.
What he had triggered was pull to refresh, a browser gesture with nothing to do with the game. It only asks that the page be at the top and that the drag be downward and long enough. Inside a list you scroll by dragging, that is exactly what a thumb does when it overshoots. I reproduced it four times in a row on menangbet before I trusted the recording.
A reload is more expensive than it looks, because everything held in memory goes with it: the round clock, the moves that were never sent, the audio graph. A dropped socket keeps your local state and can replay it; a reload cannot, and the player cannot tell the two apart, since both land on the same screen.…