WHEEL CHECK / 03

Scroll wheel test.

Check both directions. Get a clear result.

This mouse scroll test flags reversed signals and shows the exact event. Roll toward you in phase 1, then away in phase 2.

CONTROLLED DIRECTION CHECK

Test both scroll wheel directions

READY / PHASE 1
Start phase 1Roll the top of the wheel toward you
8 EVENTS / DIRECTION MINIMUM0 / 8

Keep the cursor here. Roll toward you in phase 1; finish and let the wheel stop. In phase 2, roll away from you. Collect at least 8 vertical events in each phase. The page stays still while recording.

No events are counted until you start.

LIVE PROTOCOL

Two direction phases

PHASE 1Roll toward youReady
Vertical0Reversed0Horizontal0
No events yet
PHASE 2Roll away from youLocked
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 phase 1 toward you, then phase 2 away from you, to compare both directions.

Next: Start phase 1 toward you.

Phase 1 events0Phase 2 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. How the scroll wheel test decides.
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.

READ THE SIGNAL / WORKED EXAMPLES

What does a scroll wheel test result look like?

These are illustrative sequences, not your recorded results. Each symbol is one vertical event; read left to right.

EXAMPLE 01 / CONSISTENT

Both directions reported consistently

1 · Toward you+ + + + + + + +
2 · Away from you− − − − − − − −

8 + 8 events. Zero reversals. Each phase keeps its own sign, and the references are opposite. The two directions pass this test.

EXAMPLE 02 / REVERSED EVENT

Unexpected direction change observed

1 · Toward you+ + + + − + + +
2 · Away from you− − − − − − − −

1 reversal at phase 1, event #5. That signal opposes the first event in the same one-way phase. Repeat with the same physical motion to check whether it returns.

What if both phases match, or the sample is too short?
8 positive events in both phases
The two directions did not separate. Neither phase reversed, but the references match. Reset and use opposite physical motions.
Only 7 vertical events in a phase
No complete protocol yet. Retry that phase and collect at least 8. A zero-event phase is reported as “One direction was not observed.”

Your signs may be the reverse of these examples, including with natural scrolling. The same rule applies: steady within each phase, opposite between phases.

RETEST / ONE CHANGE AT A TIME

Compare the scroll test after one change

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.

No complete result to export yet. Finish both direction phases or a rate sample.

Preview the exact report before copying or downloading
No complete result to export yet.

Reports include the current complete test and saved A/B, with each test included once. Reset clears the live direction test; Clear A/B removes only the saved comparison.

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. Use the app-specific troubleshooting path to narrow it down.

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 input check, reconnect the device and compare another app or computer.

SPEED FEELS WRONG

Review the setting before blaming hardware

Check the mouse scroll settings for your system, then repeat the same motion. Keep the wheel mode and app the same while comparing.

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 compare your toward-you and away-from-you actions. Natural scrolling can swap the signs without changing the rule.
  3. The result describes this browser protocol.Save one condition as A, change one condition for B, and keep the named results and exact events for troubleshooting.

Need the measurement details? Read the scroll test method, event units and measurement scope. For repeated jumping or missing input, work through the scroll-wheel troubleshooting guide.