TinyFingers tools

Mouse test

Check your buttons, hold, drag and scroll. See what your browser receives.

Ready to test

Use your mouse inside the area below. Hold a button and move, then scroll in both directions.

Click, hold, drag & scroll here The picture shows logical buttons. Your physical layout may differ.
Button presses received0No button held
Hold and moveNot observedMovement while a button is held
Wheel directions receivedNot observedBrowser events, not physical wheel notches

Device type is your selection: a browser cannot reliably distinguish a mouse from a trackpad. Side buttons may still trigger browser navigation.

Button details
Primary usually left
Not observed
Secondary usually right
Not observed
Middle wheel press
Not observed
Extra 1 if exposed
Not observed
Extra 2 if exposed
Not observed
Last completed hold
Longest completed hold
Releases observed
0
Holds ended by an interruption
0
Scroll direction changes
0 vertical · 0 horizontal

Completed holds and test interruptions stay separate. A release does not reveal whether you intended it.

Scroll direction changes compare consecutive non-zero values on each axis during one uninterrupted observation. Gestures, momentum and natural scrolling can also reverse direction.

How to test your mouse

  1. Choose the device you are actually using. Keep a trackpad test separate from a mouse test.
  2. Put the pointer in the test area and press each available button once. Try the wheel as a button as well as a scroll control.
  3. Hold one button, move the pointer inside the area, then release. Look for “Held” during the action and “Detected” after release. Repeat with another button if useful.
  4. Scroll both ways inside the area. Try sideways scrolling if your device supports it. Move outside the area to scroll the page normally.
  5. Review the observations. Download a local report if you want to compare another connection or application.

What the results mean

Detected means the browser received a press for that logical button. It does not certify the physical switch. Not observed means no matching press reached this test; the button may be absent, reassigned, intercepted or simply untested.

Hold and move records pointer movement while at least one button is held. The last and longest completed holds use the browser’s event timestamps. A release is counted separately from a hold ended because you left the area or changed windows. It does not reveal whether a release was intentional, measure a sensor’s accuracy or prove that a long drag will never disconnect. Leaving the area or changing windows ends the current hold observation so the drawing cannot remain stuck.

Wheel directions describe the sign of scroll changes received by this page. The value can be reported in pixels, lines or pages. One browser event is not one physical notch, and trackpad gestures can generate the same kind of event. System settings can reverse the relationship between your gesture and the reported direction.

Something looks wrong? Check this next

ObservationUseful next check
A button stays unobservedCheck its assignment in your system or mouse software. Try the same action in another application and another browser.
Left and right appear swappedCheck the primary-button setting. This test labels logical actions, so a left-handed configuration can be working as intended.
A hold ends unexpectedlyRepeat entirely inside the test area without switching windows. If it also happens elsewhere, compare another port, connection or device.
One press seems to click twiceUse the double-click observation test with deliberate, spaced single presses.
Wheel input is missing or changes directionCheck scroll settings, then compare another application. A trackpad’s momentum and gestures can produce additional scroll events.

Compatibility and limits

This tool needs a browser that exposes Pointer Events and wheel events. Touches and pen input are identified separately and do not increase the mouse-button counter. A trackpad may report itself as a mouse; the device selector records your stated test context, not automatic hardware identification.

Extra buttons are shown only when the browser exposes their logical signals. Some buttons run a system shortcut or navigate away before the page can observe them. The test handles context menus only inside its area; your browser’s commands remain available elsewhere.

These observations cannot certify a model, polling rate, latency or electrical fault. Read our testing method and validation limits before treating a result as a hardware conclusion.

Do clicks leave my device?

The test processes button and scroll observations in this page’s memory. It does not upload your input, store a movement history or identify your device. Resetting or leaving clears the observations. A report is created locally only when you download it. TinyFingers uses its existing Google Analytics for general page and tool usage; input details are not sent. About TinyFingers and privacy.