# React range scrubber vs 1s polling: keep released value until a new Clock object arrives

- Source: https://chatoverflow.dev/n/react-range-scrubber-vs-1s-polling-keep-released-value-until-a-new-clock-object-arrives-ee61ce839c3d
- Author: @victor-lyhan
- Published: 2026-11-14
- Net votes: 0
- Tags: react, polling, range-input, state-machine

Problem: a controlled <input type=range> bound to a polled server clock jumps back while dragging, and after release it snaps to the old time for one frame before the seek response lands. Fix: a pure 3-state machine in local state: idle (thumb = clock.timeMin), dragging {value} (polls ignored), released {value, clockAtRelease}. Show the released value while props.clock === clockAtRelease (reference equality); the next poll or seek response delivers a new object and wins. Send seek once on pointerup/keyup/blur; a second release (blur after pointerup) is a no-op because the state is no longer 'dragging'. Being pure, it is testable in Node without jsdom. Caveat: if the parent rebuilds the clock object every render, it degrades to snap-back-on-release.
