Mouse Scroll Wheel Test: Check Direction and Events
Place the pointer in the test area, scroll slowly in each direction and inspect the received wheel events.
Results
—
How to read wheel direction and deltas
Place the pointer in the test area and turn the wheel slowly upward, pause, then turn it downward. The counter includes only wheel events this area receives. Button presses are counted apart from wheel movement.
Vertical delta is the up-down part, and horizontal delta appears when the browser sends it. The sign is direction in this event system. Mode 0 means pixels, 1 means lines, and 2 means pages; a value of 120 in pixel mode is 120 CSS pixels, not 120 notches.
Common questions
Why do the numbers not match the notches I feel?
The page never sees notches. With mode 0, the value is CSS pixels of reported movement. The browser and the system can scale that step.
How can I check a reversed direction?
Take about ten slow steps one way, with a pause between them, and watch whether the sign flips. Smooth scrolling can move the page differently from the events.
Can this identify a bad encoder?
No. It does not inspect the encoder or explain a dropped connection. A trackpad can also emit wheel events, so note which device you used.
Check wheel direction with deliberate steps
Place the pointer inside the active test area and turn the wheel slowly upward. Pause, then scroll downward. The wheel event counter records events received by this area. Use Clear results before a second comparison. Buttons are counted separately from wheel movement.
Read the event values
Open Details and event log to inspect recent wheel values. The vertical component is deltaY; deltaX describes horizontal movement when the device and browser expose it. A positive or negative sign describes the reported direction in this event system. Watch a sequence of slow steps to see whether unexpected reversals repeat.
The deltaMode field defines the units: 0 means pixels, 1 means lines and 2 means pages. A value of 120 with deltaMode 0 therefore describes 120 CSS pixels of reported movement. It does not prove that the wheel moved 120 notches. Browsers and system scrolling settings can produce different numerical values for the same physical action.
Compare a suspected reversal
Try ten slow steps in one direction with a complete pause between them. Repeat in an ordinary long document and, if needed, another browser. Smooth scrolling or a page script can change visible page motion even when received direction events are consistent. If reverse events follow one mouse across applications and computers, keep that log for manufacturer support.
Limits of this check
This test receives browser wheel events. It does not inspect the wheel encoder, measure USB polling rate or identify the cause of a connection interruption. An ordinary trackpad can also generate wheel events, so record which input device you used.