Scroll wheel troubleshooting guide

1. Select detented mouse, free-spin mouse, touchpad, or unknown.
2. Use the diagnostic mode and scroll steadily down only for the requested phase.
3. Stop fully during the pause, then scroll steadily up only.
4. Repeat at your normal pace and once at a faster but controlled pace.
5. Keep the tab visible. Discard a run flagged as interrupted or delayed by more than 250 ms.
6. Repeat the same protocol at least three times before comparing patterns.

Record the declared setup and input-device connection, browser and OS, delta units, reversals, horizontal-only and true-zero counts, gaps, bursts, actual duration, validity, and callback delay. The measurement methodology explains exactly what those observations can and cannot mean.

First separate a configured direction from an unintended reversal. “Natural scrolling” and similar OS settings can reverse the relationship between finger or wheel motion and page movement consistently. That is a preference, not an intermittent fault.

• Confirm the operating system's scroll-direction setting and whether it recently changed.
• In the diagnostic, declare the intended phase and look for isolated opposite-direction events.
• Let touchpad momentum stop before changing direction; overlapping gestures can produce a reversal.
• Repeat in a second browser and, if possible, the same device on another computer.
• Try a known-good mouse on the original computer to separate device and software context.

A repeated reversal pattern across browsers and computers is useful evidence for support, but it still is not proof of a specific encoder failure. Export the local diagnostic report and describe the physical action you intended.

A browser trace can reveal long delivery gaps between received events. It cannot observe a physical movement that generated no event, so count your deliberate actions separately if you need to investigate missing inputs.

• Check battery level, cable seating, wireless receiver placement, and obvious connection warnings.
• Close CPU-heavy pages or applications, then repeat without switching tabs.
• Test a plain document or settings panel to see whether the symptom is browser-specific.
• Review accessibility, mouse, and scrolling utilities that may transform input.
• Use only the device maker's documented, power-safe cleaning process.

If the wheel is nonresponsive in multiple applications and on another computer, contact the manufacturer or a qualified repair service. A website cannot safely identify the internal component at fault.

Closely spaced browser events can come from fast input, free-spin momentum, OS acceleration, driver behavior, browser coalescing, or delayed main-thread delivery. Select free-spin when the wheel is unlocked; comparing it with a detented run as if they used the same protocol is misleading.

• Check whether a mechanical or software wheel-mode switch changed from detented to free-spin.
• Temporarily review OS and vendor scrolling or acceleration settings; note changes before retesting.
• Compare event rate and delta movement separately instead of treating either as physical notch count.
• Repeat at a slower, steady pace to see whether the burst pattern persists.

Touchpads commonly continue producing wheel events after fingers lift, and a browser cannot reliably infer where one physical gesture ends. Pinch, multi-finger, accessibility, and OS gestures may also be intercepted or transformed before the page sees them.

Select touchpad, use one consistent two-finger gesture, and wait for momentum to end before the opposite-direction phase. Do not compare a touchpad result with a mouse challenge score. The input comparison guide explains why their browser traces differ.

A horizontal wheel or tilt action normally appears in the browser-reported horizontal delta, but applications and drivers may map it differently. Check deltaX while making only the intended horizontal action. Retest in a horizontally scrollable document and review device software mappings.

Middle-click is a button event, not a wheel delta. This scroll diagnostic does not test middle-click continuity, drag behavior, or button switches, so a clean wheel trace says nothing about those functions.

Change one variable at a time and label each report. See browser compatibility before interpreting differences between browser runs.

Stop using the device if it is physically damaged, unusually hot, leaking, swollen, smells abnormal, or creates an electrical concern. Disconnect it safely when the manufacturer's guidance permits and seek qualified support. For ordinary input symptoms, a concise report with the device category, connection type, browser, OS, protocol, and repeated observations is more useful than a claim that a browser test “proved” the hardware is broken.