A mouse scroll test on Windows is a browser check that records finite wheel-event values delivered while your pointer is inside a focused test area. Use the Mouse Scroll Test while moving a mouse wheel or making a trackpad gesture, then compare the total event count, the up, down, left, right, and none buckets, the latest horizontal and vertical deltas, and the signed cumulative X and Y totals. It is useful when you need to confirm which directional wheel events reach a browser on Windows, see whether one axis is missing, or repeat the same check under controlled conditions. The test does not repair Windows, calibrate physical scroll distance, or diagnose mouse hardware. Its evidence is deliberately narrow: it shows what this browser delivered to this page during the current tab session. Keep the pointer over the dashed zone, use several short movements in each direction, and reset between runs when you want a clean comparison.
What the Windows browser check measures
The page records finite WheelEvent deltaX and deltaY values only when an event is delivered inside one visible dashed test zone. That boundary matters: a result can confirm what reached this browser target, but it cannot establish what every Windows application, background service, or operating-system control receives. A browser may also combine, smooth, accelerate, or suppress wheel events before the page sees them.
Events delivered to the zone have their normal page scrolling prevented, so the target remains in place during the check. Gestures outside the zone behave normally and are not counted. The area can display a focus outline, but keyboard arrow keys are not treated as wheel input. Touch scrolling that does not generate a wheel event will not appear.
Run a mouse scroll test on Windows
Use one browser and one mouse or trackpad for a clear baseline:
- Open the test and position the pointer. Load Mouse Scroll Test in the browser on your Windows computer, then place the pointer over the dashed test area. Keep it there for every gesture you intend to count.
- Test vertical wheel movement. Make several short upward movements, pause, and then make several short downward movements. Separating the movements makes it easier to associate each change with the gesture you performed.
- Test horizontal input when available. Use left and right trackpad gestures, or use a tilt wheel if your device provides horizontal wheel input. A traditional vertical wheel will usually produce up and down events but may not produce horizontal deltas.
- Inspect the latest delta pair. After each movement, compare the displayed horizontal and vertical values with the direction you attempted. A diagonal gesture can produce nonzero values on both axes.
- Check the event record. Compare the total event count with the separate up, down, left, right, and none buckets. This shows how many accepted events arrived and which dominant-axis label each one received.
- Repeat under consistent conditions. Run the same short movements slowly and quickly while keeping the browser, operating system, mouse or trackpad settings, and input method unchanged. Note whether the labels follow your gestures and whether the browser groups or changes the events.
- Reset the session. Select Reset test after recording a run. Every event count, directional bucket, and cumulative total returns to zero for the next comparison.
If an application behaves differently from this page, investigate that target separately. The result here proves only which wheel events reached this browser page during the current session.
Read the live result fields correctly
The result separates event activity from raw axis values and signed sums, so a large cumulative number is not the only measure of scrolling.
| Result field | What it represents | What to compare |
|---|---|---|
| Total events | Every accepted wheel event delivered to the zone during the current session, including a zero-delta event. | Compare it with the sum of activity visible across the direction buckets. |
| Directional buckets | Separate counts labeled up, down, left, right, or none, with one dominant-axis bucket assigned to each event. | Check whether the recorded directions match the gestures attempted. |
| Latest delta pair | The most recent accepted raw horizontal and vertical values. | Inspect both axes immediately after each movement. |
| Cumulative X and Y | Signed sums of the raw horizontal and vertical deltas in the current session. | Use them as raw sums, not as distance or a count of movements. |
| Reset test | A control that clears all counts and totals for a new local session. | Use it between runs after recording the previous result. |
Only finite delta pairs are accepted. A delivered zero pair remains visible in the total and none bucket. Non-finite synthetic deltas are rejected, and counter overflow is guarded rather than displayed as a misleading value. Because cumulative X and Y are signed sums, opposite movements can bring a total near zero even while the directional and total event counts continue to rise.
Apply the direction-labeling rule
Every accepted event receives one visible label based on the larger absolute axis value.
| Delta condition | Direction bucket |
|---|---|
| Both deltaX and deltaY are zero | none |
| The absolute vertical value is at least the absolute horizontal value, and deltaY is nonzero | up or down, selected according to the sign of deltaY |
| The absolute horizontal value is greater than the absolute vertical value | left or right, selected according to the sign of deltaX |
Equal nonzero magnitudes deliberately choose the vertical branch, so the sign of deltaY determines the up or down label. The single bucket does not mean that a diagonal gesture contained movement on only one axis. Both raw values can remain nonzero, which is why the latest delta pair must be considered alongside the direction label.
Compare Windows input methods fairly
The input method helps explain what you may see, but it does not turn the browser values into a hardware measurement:
- Traditional vertical wheel: Usually produces up and down events. The absence of horizontal events may reflect the device’s capabilities rather than a fault.
- Two-axis trackpad: Can produce horizontal, vertical, or diagonal delta pairs. Compare the raw X and Y values before focusing on the single direction bucket.
- Tilt wheel: May expose horizontal deltas when the hardware, settings, and browser deliver them.
- Touch input: Appears only when the interaction generates a wheel event. Touch movement that creates no wheel event is outside what this page records.
- Keyboard arrows: Do not count as wheel input, even when the test area has a visible focus outline.
Raw deltas can represent pixels, lines, pages, or another browser-defined unit. Different browsers, operating systems, drivers, wheels, trackpads, accessibility software, settings, and hardware can produce different magnitudes for movements that feel similar. The tool intentionally does not convert values into centimeters, wheel notches, screen pixels traveled, or a normalized cross-device score.
Compare the latest direction label with the gesture first, then check the directional counts and total event count. Do not treat cumulative X or Y near zero as proof that no scrolling occurred, because opposite signed movements can cancel.
What the result can and cannot prove
A missing direction can result from device capability, browser interception, gesture settings, remote-desktop software, or the test method. The page does not identify which factor caused the absence. A normal event confirms that the browser delivered a finite wheel event to this target during the session; it does not prove that another program will handle input identically.
This tool is not a mouse polling-rate checker, input-latency test, hardware diagnostic, repair guide, or accessibility assessment. Browser wheel events cannot reveal a USB polling frequency, physical encoder bounce, radio quality, driver health, or the exact moment a wheel moved. Use manufacturer diagnostics or qualified support when a hardware decision depends on the result.
Local session behavior
All event counts and deltas stay in the current tab. The widget does not upload gestures, save history, identify the device, request hardware permissions, or listen outside its test area. Refreshing the page, closing it, or selecting Reset test clears the session.
For a deeper look, see Mouse Click Test: Verify One Press per Button.