Discrete step scrolling and pixel-level smooth scrolling

What it is

Discrete scrolling converts a wheel notch or key input into a jump of a fixed number of lines or pages. Pixel-level smooth scrolling updates content with small continuous displacements, typically from trackpads, touchscreens, or high-resolution wheels. The distinction decides whether people see a sequence of position jumps or continuous motion.

Why it happens

Discrete input naturally supplies counts, which the system accumulates by step size. Smooth input supplies denser displacement or velocity data, which the system interpolates or applies directly. Steps aid exact movement by line, paragraph, or list item; smooth motion preserves visual continuity and context. Rendering, frame rate, scroll containers, and input hardware jointly determine the result.

The difference traces back to what the hardware itself reports. A mechanical wheel is divided into fixed angular detents, firing one discrete event per click, which the OS then translates into pixels or lines. Trackpad and touchscreen sensors continuously sample contact displacement, producing continuous values natively — the system should not first quantise that into detents and then re-expand it, since doing so throws away information carried in the finger's actual speed. This is also why the feel changes abruptly when a device gets a different peripheral: plug an old mechanical-wheel mouse into a laptop and scrolling instantly reverts from continuous to stepped — not a software bug, but a change in the granularity of the upstream data source itself.

Studying it

Compare step size, smoothness, and devices in reading, search, precise alignment, and long-distance browsing. Measure location time, backtracking, reading interruption, motion discomfort, and input-display latency. Test text, card lists, and canvases separately; one webpage's result does not represent all content. When comparing discrete and smooth modes, also control for perceived total displacement — if a smooth mode's acceleration curve makes the same wheel rotation travel farther, the measured difference may come from distance rather than from the scrolling style itself.

Where it stops holding

Smooth is not always better: line-by-line review, code editing, and discrete-item browsing can make excessive inertia and interpolation hard to stop precisely. Unstable animation on low-performance devices can be more disruptive than instantaneous stepping — when the render frame rate cannot keep up with the interpolation cadence, the picture tears or stutters, and "smooth" ends up manufacturing a new perception of instability. Applications should not override system-level scroll settings or assistive preferences; for instance, an OS-level "reduce motion" setting should also disable scroll interpolation animation.

Applying it

• Support appropriate stepping and continuous offsets based on the content task rather than forcing one scroll feel across all devices; identify the input source's native granularity (discrete detents vs. continuous displacement) and do not fabricate false smoothness by interpolating discrete input.
• Keep input-to-visual latency low; do not let content catch up in a burst after fingers or wheel stop.
• How to check: test reading location, list revisitation, and exact stopping across devices, logging backtracking and missed stops; specifically test low-performance devices for tearing or dropped frames introduced by interpolation animation.

Related

• Same group: C1.11.2 Inertial scrolling friction and stopping expectations · C1.11.3 Scroll-position jumps and anchoring under asynchronous loading · C1.11.4 Scroll hijacking breaks expectations of user control
• Nearby: C1.08 Drag and drop · I1 State, time, and response
• Search terms: smooth scrolling · discrete scrolling · input granularity