WheelEvent activity tail

Wheel-spin capture run

idle
Upper trace · negative deltaYLower trace · positive deltaYNo input · flat line
Start, then make one fast, directed wheel spin.The release button is a user marker, not a hardware sensor event. Touch-only devices without wheel input may produce no events.
Captured activity
User release timeNot marked
Events before release0
Events after release0
Active tail after release0 ms
Peak browser event rate0 events/s
Median / p95 interval
Peak |delta|
Reverse candidates0
Cumulative |delta| by mode
1 time buckets; peak aggregate absolute delta 1.0. The x-axis is elapsed time; the y-axis is summed |deltaY| per 100 ms bucket. The end line marks session completion.
The summary stays in this browser and is not uploaded.

This is a browser-level observation, not a laboratory measurement or a definitive hardware diagnosis. Read the disclaimer.

Free-Spin Scroll Test

Run a free-spin scroll test to inspect the browser event tail produced by one fast, directed wheel motion. Mark when your finger leaves the wheel, then review duration, event rate, delta activity, decay, and reverse candidates locally.

The release marker comes from you

A browser receives wheel events but has no sensor event that says when your finger physically left the wheel. Released wheel records your chosen moment; the tool then observes the remaining event tail until a documented quiet gap.

How to use the Free-Spin Scroll Test

Select a genuinely separate run

Choose Free Spin for a freely rotating mode or Ratchet / Notched Comparison for a new notched run. Reset between modes so their samples never blend.

Flick, release, and mark

Start with the pointer inside the capture area, move the wheel quickly in one direction, lift your finger, and immediately choose Released wheel. The button is a user marker, not a device reading.

Let the tail become quiet

Keep the pointer in place until auto-stop follows 800, 1200, or 1500 ms without an event, or finish manually. Review the chart and repeat under the same conditions.

What free-spin and infinite scrolling mean

Free-spin commonly describes a wheel mode with little ratchet resistance, allowing momentum to continue after the finger releases. Product interfaces may call related behavior infinite scroll, hyper-fast scrolling, smooth wheel, or free scrolling. Those names do not define a web standard. The free spin mouse wheel test records only the WheelEvent sequence exposed to this page, so it can describe an activity tail without confirming a wheel mechanism, bearing, encoder, or manufacturer mode.

Ratchet mode usually creates more deliberate tactile steps, while free-spin may create a dense burst and a longer decay. Driver and operating-system processing can make the browser patterns overlap. The optional notched comparison is therefore a separate run, not an automatic classification. Use the same direction, browser, and settings, reset between runs, and describe the observed difference instead of declaring that one trace proves a particular product feature.

How the mouse wheel spin test captures a tail

The session starts only after you press Start and captures events only in the focused area. Every sample retains elapsed time, delta axes, deltaMode, and modifier states in a bounded buffer. Pressing Released wheel saves the current elapsed time. The listener remains active until the selected quiet period passes after the most recent event or you finish manually. Quiet time is a protocol setting, not evidence that the physical wheel stopped at that exact instant.

A 100 ms bucket combines absolute deltaY for the decay chart and counts events for the peak browser event rate. The chart marks the user release and session end. A steep early peak followed by smaller buckets is one possible decay shape; an irregular shape may reflect input technique, browser scheduling, driver processing, or a change in direction. The visualization reports the trace and avoids animations that could obscure individual changes.

How to read duration, rate, and decay metrics

Total captured duration spans the first through last browser event. User-marked release time is your button press, while events before and after release divide the samples around that marker. Active tail duration measures from the marker to the last captured post-release event. Peak browser event rate is the busiest chart bucket converted to events per second; it is not USB polling rate or the wheel's internal scan rate.

Median interval describes typical event spacing, and p95 interval highlights a slower edge without letting one maximum dominate. Peak absolute delta and cumulative absolute delta remain raw values grouped by deltaMode. Pixel, line, and page totals stay separate because they are incompatible units. Reverse candidates have a sign opposite the run's dominant direction, but they do not by themselves identify encoder failure, bounce, or wear.

Useful free scrolling mouse test scenarios

People use an infinite scroll wheel test when a long document stops sooner than expected, when momentum feels different after a driver update, or when two wheel modes need a repeatable browser-level comparison. Web developers can inspect whether a virtual list receives a burst and a long tail. Support teams can compare a run before and after reconnecting a device. Reviewers can publish a transparent trace rather than an invented revolution count or unsupported distance estimate.

This hyper fast scroll test also helps distinguish a wheel-tail question from page performance. If the chart continues but content stutters, the application may be doing expensive work. If events end cleanly here but another app keeps moving, application inertia may be involved. These are troubleshooting directions, not diagnoses. Pair this tool with the scroll speed test, sensitivity test, comparison test, or raw wheel event tester depending on the question.

Browser limitations and repeatable technique

The browser cannot know the instant of finger release, physical spin duration, wheel revolutions, circumference distance, encoder resolution, or device model. Background throttling, lost focus, modifier keys, natural scrolling, battery state, wireless conditions, drivers, and system line settings can alter the stream. Even with the same setup, hand force varies. Treat repeated, similarly shaped sessions as stronger evidence than one dramatic spin.

For better repeatability, use a stable grip, choose one direction, avoid touching the wheel again after release, and press the marker promptly. Keep browser zoom and system settings fixed. If auto-stop occurs too soon, select a longer quiet gap before the next run. If the page sees nothing, verify pointer position and focus, try the wheel event tester, and compare another browser. Never spin so aggressively that the device or your hand is at risk.

Local processing, related tools, and disclaimer

The free-spin scroll test processes raw samples and draws its lightweight SVG chart locally. A completed summary can be saved on this device only when you use the opt-in save control. No account is required, and the test does not fingerprint a mouse model or inspect operating-system sensitivity. Reset clears the current in-memory run so a ratchet comparison begins independently.

This free spin mouse wheel test describes browser-received input in the present device, driver, operating-system, settings, browser, and user-action context. It is not a definitive hardware diagnosis or a manufacturer benchmark. Consult the testing disclaimer and official device guidance before making repair, warranty, or purchasing decisions from an unusual tail.

Free-Spin Scroll Test questions

Does Released wheel detect my finger automatically?

No. It stores the moment you press the button. Standard WheelEvent does not expose a physical finger-release signal.

Is peak event rate the wheel polling rate?

No. It is the busiest browser-received 100 ms bucket expressed per second, after the full input pipeline.

Why are cumulative deltas separated by mode?

Pixel, line, and page deltaMode values are different units, so combining them into one raw magnitude would be misleading.

Can a notched wheel use this test?

Yes, as an independent Ratchet / Notched Comparison run. The result describes its browser trace without classifying hardware.