mousecheck.

WHEEL CHECK / 03

Scroll wheel test.

Check both directions, then get a conclusion you can act on.

The guided test records one physical direction at a time. It tells you whether down and up produced separate, internally consistent browser signals—and shows the exact event if a direction changed.

  1. 01

    Roll down only. Move the wheel away from you until at least eight vertical events arrive.

  2. 02

    Roll up only. Move toward you in a separate phase—do not reverse inside either phase.

  3. 03

    Read the result. We check each phase for reversals, then check whether the two directions separated.

CONTROLLED DIRECTION CHECK

Down first. Up second.

READY / DOWN PHASE
Start the down phaseThen roll away from you inside this area
8 EVENTS / DIRECTION MINIMUM0 / 8

Keep the cursor in the dotted area. During each phase, move in the named physical direction only. The page is locked from scrolling while it records, and Ctrl-modified zoom-style input is excluded.

No events are counted until you start.

LIVE PROTOCOL

Two direction phases

PHASE 1Roll down / awayReady
Vertical0Reversed0Horizontal0
No events yet
PHASE 2Roll up / towardLocked
Vertical0Reversed0Horizontal0
Complete phase 1 first

phase direction reversed horizontal only Equal spacing shows order, not time or strength.

YOUR RESULT / THIS PROTOCOL

No complete protocol yet

Complete the down phase, then the up phase, to compare both directions.

Next: Start with the down phase.

Down events0Up events0Reversals0Reference signs— / —
Our rule: each stopped phase needs at least eight nonzero vertical browser events. Signals must stay with that phase’s first sign, and the two phase reference signs must be opposite. Eight is this page’s sampling minimum, not a hardware standard. Read the method.
Inspect exact wheel events0 EVENTS

Elapsed time starts when each phase starts. Pixel, line and page values keep their own browser-reported unit and are never added into one physical distance. The latest 80 events are shown.

  1. No wheel events recorded in this protocol.

RETEST / ONE CHANGE AT A TIME

Does the same pattern return?

Save a complete protocol as A. Reset, change one condition—browser, connection, computer or mouse—then repeat the same physical actions for B.

Only a complete two-direction protocol can be saved. Saved results stay in this open page until reload or Clear A/B.

Complete the direction check to create protocol A.

OPTIONAL SPEED SAMPLE

Five-second browser event rate

This measures how many vertical wheel events this browser receives in five seconds. It is not mouse polling rate, physical notches per second or a universal quality score.

READYStart, then scroll one way here

The timer begins with the first vertical event.

RATE RESULT

No complete sample yet

Use one steady physical direction for the whole five-second window.

Vertical events0Events / second—Positive / negative0 / 0Reported units—
Use this number only for like-for-like repeats in the same browser and setup. Device, operating system, application and input mode can all change the events the browser receives.

USE THE RESULT

What your result means next

The page answers what reached this browser. The next check depends on where the symptom appears and whether it repeats.

CONSISTENT HERE

Both directions reported consistently

If one game or app still fails, inspect that app’s bindings, overlays and input settings. A clean browser sample does not validate another application.

REVERSED SIGNAL

An unexpected change appeared

Repeat the same protocol as B after one change. If the same phase reverses again, continue with the scroll-wheel troubleshooting path.

NO / SHORT INPUT

One direction was not verified

Keep the cursor in the area and retry. If no vertical event arrives, use the complete mouse test, reconnect the device and compare another app or computer.

SPEED FEELS WRONG

Review the setting before blaming hardware

macOS exposes scroll speed under Accessibility pointer controls. Windows exposes scroll amount and direction under Bluetooth & devices → Mouse.

HOW THIS TEST DECIDES

Physical direction is declared. Browser direction is observed.

  1. The first vertical event sets a phase reference.Later vertical events in that same one-way phase are marked same or opposite. Horizontal-only events stay separate.
  2. The opposite physical phase must use the opposite sign.We do not assume positive means “down” for every setup. We only expect your declared down and up actions to separate.
  3. The result describes this browser protocol.A repeated pattern across controlled A/B runs is stronger evidence than one sample, but still does not reveal the physical cause.

MEASUREMENT BOUNDARY

A browser event is not a physical wheel notch.

A mouse wheel, free-spin wheel, trackpad or another equivalent input can produce the same event. This page cannot see a detent that produced no browser event, inspect an encoder, read firmware or USB reports, or prove why an application behaves differently. A wheel event also need not scroll page content, and its delta values do not necessarily match content movement.

Method sources: W3C Pointer Events · MDN WheelEvent · Settings: Apple Support · Microsoft Support · General troubleshooting: Logitech Support.