Scroll Wheel Step Test

The scroll wheel step test records standard `WheelEvent` messages only while its capture area is active. Each record contains a relative timestamp, delta axes, `deltaMode`, direction sign, and modifier-key state. Events separated by less than the selected inactivity threshold become one captured event group. The result can therefore tell you whether an instructed action produced no group, one browser event, or several closely timed events. It cannot see the encoder, count teeth, or confirm how many physical detents moved.

The words wheel notch test and mouse wheel step test are useful search terms, but they can imply a one-to-one relationship that web APIs do not promise. A driver may transform one movement, a browser may dispatch several events, and smooth devices may have no tactile notch at all. This wheel step checker treats the browser stream as the evidence and leaves the physical mechanism unknown. That boundary makes repeated observations more honest and easier to compare.

Grouping begins with time, not raw magnitude. When the gap after an event exceeds the configured threshold, the next event starts another group. For each group the tool saves start and end time, duration, event count, summed deltaX and deltaY, largest and median absolute deltaY, positive and negative signs, modifier keys, and every deltaMode seen. The threshold can change segmentation, so include it whenever you share a scroll notch consistency result.

Median is the middle value after sorting and resists one unusually large group better than a mean. The interquartile range, or IQR, covers the middle half of values. Median absolute deviation, or MAD, describes the typical distance from the median. Low spread can indicate that browser-received magnitudes were similar in this run; it does not grade the wheel. Magnitude statistics are disabled when groups mix pixel, line, or page units because those raw units are not interchangeable.

Captured groups shows how many separate bursts reached the page. Groups with one event and groups with multiple events describe dispatch shape, while median group duration and median inter-group interval describe timing. Dominant direction reports the most common deltaY sign. A reverse candidate is a group whose sign opposes the direction you requested. Natural-scrolling preferences can alter how hand movement relates to content movement, so use the on-screen Up or Down instruction consistently rather than assuming a universal sign.

If you select Record & next without a new group, the exact result is: no browser event group was captured for this attempt. That observation is deliberately not called a missed hardware notch. The pointer may have left the area, the action may not have reached the browser, focus may have changed, or the physical motion may have been too small. Repeat the protocol and check the raw wheel event tester before deciding whether the absence is reproducible.

A player can compare controlled wheel actions when a game binding appears to skip. A developer can inspect whether a web interface receives bursts rather than single events. Support staff can ask for the same attempt count and gap threshold before and after a setting change. Accessibility users can document how remapping software reaches a browser. Reviewers can describe event patterns without inventing a universal good score. In every case, the useful unit is a repeated browser-observed attempt, not an assumed mechanical click.

The wheel notch test is also useful after changing an operating-system line setting, installing an official driver update, or moving between browsers. Test one change at a time. Keep the device, port, browser zoom, page focus, requested direction, and hand technique stable. Save a local summary if you need a record, but avoid comparing raw delta magnitude across computers unless deltaMode and the rest of the environment are controlled.

WheelEvent values are processed through device firmware, drivers, the operating system, browser settings, and application logic before this page sees them. The scroll wheel step test does not measure hardware polling rate, encoder resolution, physical circumference, USB report rate, or wear. It also cannot reliably identify whether input came from a mouse, trackpad, trackball, remote session, or accessibility device. A candidate is an invitation to repeat, not a diagnosis.

For a cleaner run, keep the tab visible, place the pointer in the capture card, avoid modifier keys, and pause clearly after each action. If groups merge, increase the pause before changing the gap threshold. If no events appear, test the main scroll wheel test and raw event tester, review application remapping, reconnect the device safely, and try another browser. Follow manufacturer guidance for cleaning; do not open a device or apply liquid because of a web result.

Event grouping and calculations happen in this browser. The active raw stream is bounded and is not uploaded by the tool. Optional saved results contain a versioned summary in local storage rather than a complete event trace. Use the scroll direction test for calibrated signs, the scroll jitter test for isolated reversals, the scroll speed test for fixed-time rate, the scroll wheel comparison test for two locked runs, and the troubleshooting guide when behavior differs between applications.

Results from this mouse wheel step test describe browser-observed groups under the current device, settings, operating system, and browser. They are not proof of physical notch count or a definitive hardware diagnosis. Read the site testing disclaimer before using a result for support, repair, warranty, or purchasing decisions.