Track length sets reachable precision

What it is

A track offers only so many pixels (or touch samples) to stop on. Mapping a set of legal values onto it means each pixel must carry some of them. The track-length precision budget says: the track can stably separate only as many notches as it is long; too short, and neighboring legal values collapse into one pixel, so no amount of care can drag them apart. The issue is the resolving power geometry can support, not whether the task should use a slider, and not whether the thumb is easy to hit.

Why it happens

A 200-pixel track expressing integers 0–1000 gives about five values per pixel. When the thumb rests on a pixel the system can only round to one of those notches; the other four are unreachable. When legal notches outnumber distinguishable pixels, the map goes from one-to-one to many-to-one. Finger jitter usually costs a few more pixels, so the effective budget is smaller than the length. Lengthening the track buys budget; shrinking it to a stub on a narrow screen drops precision on the spot. Vertical tracks are bounded by viewport height and are often tighter than horizontal ones. This is quantization, not a vague complaint that the slider “feels off.”

Studying it

Hold the number of legal values fixed, vary track length, and measure the rate of stable hits and whether neighbors can be dragged apart. Factors: pixel length, domain size, snap-to-tick. Outcomes: count of unreachable values, places that skip a notch even with a careful drag. Report domain / length as a quantization ratio; it explains more than mean error. On touch, use actual touch sampling; do not treat mouse pixels as contact precision.

Where it stops holding

When values snap to sparse ticks, the tick set—not the length—sets effective notches; length only affects how hard a tick is to hit. A typing channel is not bound by track length; a numeric field can supply values the slider cannot reach. Responsive layout that stretches the same track on desktop and stubs it on a phone lets precision change by device, so a task suddenly becomes unreachable on mobile. CSS pixels and physical pixels on a high-DPI screen are not the same; budgeting in CSS pixels overestimates resolving power.

Applying it

• Check that legal notches ≤ pixels one can stably stop on; if notches far exceed length, change the control or shrink the domain.
• Do not cram a fine desktop domain into a short mobile track unchanged.
• When values beyond the budget are required, offer typing; do not pretend dragging can reach them.
• Verify by listing must-selectable values and dragging to each on the real track length of the target device. Two neighbors that always share a stop means the budget is spent. Rotate to landscape or widen the window and see whether precision returns with length.

Related

• Within the group: E2.12.1 Sliders suit approximate values, not exact ones · E2.12.2 The current value must be shown as a live number · E2.12.4 The thumb is often below a usable hit size
• Adjacent: E2.11 Numeric input and steppers · E1.07 Button hit targets
• Search terms: track-length precision budget · slider quantization · pixel precision