Skip to content
Testpartout

Device tests · Input devices

Mouse Test

This mouse test shows which mouse inputs your browser actually receives. Start the test, then click each button, double-click, scroll the wheel and move the pointer inside the test area. Every event that arrives is listed with what the browser reported.

It is a detection check, not a repair tool. It tells you whether left, middle, right and extra buttons register, whether the wheel reports vertical and horizontal movement, how many double-clicks were detected and how far apart their presses were.

  • No time limit
  • Buttons, wheel & movement
  • No permissions required

Not listening

Start the test, then use your mouse inside this area. Nothing is recorded until you start.

The mouse test is not listening.

Detection summary

Stopped
Buttons detected
0
Total clicks
0

press + release pairs

Double-clicks
0

interval shown when measurable

Last event
No events yet

Buttons

  • Leftnot seen · 0 clicks
  • Middlenot seen · 0 clicks
  • Rightnot seen · 0 clicks
  • Backnot seen · 0 clicks
  • Forwardnot seen · 0 clicks

Wheel and movement

Wheel events
0
Scroll up
0
Scroll down
0
Horizontal
0
Last delta (x, y)
—
Pointer movement
not yet
Currently pressed
none

Text summary: No buttons detected yet. 0 double-clicks, 0 wheel events, pointer movement not detected.

A button or wheel direction that produces no event here is not proof of broken hardware, and an unexpected double-click is not an automatic verdict. The operating system, driver or browser may intercept or remap inputs. Repeat the check several times and confirm it in another application or with another mouse before drawing a conclusion.

Your result

What your result means

If a button, wheel direction or movement appears in the summary, the whole chain from the mouse to the browser is working for that input. Each press should add exactly one click when you release it.

If an input never appears, something between the hardware and this page did not deliver it — but a web page cannot tell where. A driver, a remapping utility, the operating system, the browser and a failing switch all look identical from here: no event arrives.

  • A click is counted when a press and its release are both observed, so one physical click should add one to that button's count.
  • A double-click you did not intend, or a single click counted twice, can point to a worn switch — but confirm it with repeated testing and in another application or with another mouse first.
  • The double-click interval is the time between the two primary-button presses the browser reported. Very short intervals you did not make deliberately are worth investigating further.
  • Wheel counts show direction only. Delta sizes vary between devices, browsers and operating-system settings and are not a hardware-standard unit.
  • Nothing is judged good or bad, scored, or compared against anyone.

Procedure

How the test works

  1. 01

    Start the test

    Nothing is recorded until you press “Start mouse test”. The test area then starts listening for mouse events.

  2. 02

    Click each button

    Press left, middle and right inside the area, plus any side buttons. Each button is listed with its state and click count.

  3. 03

    Try a double-click

    Double-click with the left button. The count increases and, when both presses were observed, the time between them is shown.

  4. 04

    Scroll the wheel

    Scroll up, down and, if your mouse supports it, sideways. The page does not scroll while the pointer is inside the area.

  5. 05

    Move the pointer

    Move across the area. A dot follows the last reported position so you can see that movement arrives smoothly.

  6. 06

    Reset or stop

    Reset clears everything. Stopping restores normal right-click, scrolling and middle-click behaviour in the area.

Methodology

How Testpartout measures this

The method below is exactly what the code on this page does — nothing is described that is not implemented.

What the implementation does

  • Button presses are read from mousedown events inside the test area, using MouseEvent.button: 0 left, 1 middle, 2 right, 3 back, 4 forward, and higher numbers for any further buttons the browser reports.
  • Releases are read on the whole window, so a button released after the pointer leaves the area is not left marked as pressed.
  • A click is counted only when the release of a button follows a press that was observed during the test.
  • Double-clicks come from the browser's own dblclick event for the left button. The interval is the difference between the timestamps of the two most recent left-button presses.
  • Wheel events report deltaX and deltaY; the test counts direction and shows the raw last values with their unit (pixels, lines or pages).
  • Pointer movement comes from pointermove events and is drawn as a dot at the last position inside the area.
  • The context menu, middle-click autoscroll, back/forward navigation from side buttons and page scrolling are suppressed only inside the test area and only while listening.
  • If the page loses focus or becomes hidden, pressed buttons are cleared, because release events can be missed and a button must never look permanently stuck.
  • Nothing is scored, no personal best is stored and nothing is written to your browser or sent anywhere.

Limits of a browser measurement

  • The browser only sees events the operating system and browser deliver. Some extra buttons are intercepted by drivers or the system, or are simply unmapped, and never reach this page.
  • Missing events do not prove a hardware failure. Test the same input in another application or on another computer before concluding.
  • Pointer movement is reported after acceleration, sensitivity and scaling have been applied, so it does not reflect raw sensor movement or DPI.
  • Wheel delta is not a hardware-standard unit. Values differ between mice, browsers, operating systems and scroll settings, and smooth-scrolling wheels send many small events.
  • Touchpads behave differently from physical mice: two-finger scrolling, tap-to-click and gestures may be translated into different events or none at all.
  • The double-click threshold is set by your operating system, so whether two presses become a double-click depends on that setting, not on this page.

Privacy

What happens to your data

This section describes the behaviour of the code on this page, not an intention.

  • Mouse events are processed in your browser only while the test is listening.
  • Nothing about your mouse input is saved to local storage, cookies or any server.
  • No device identifiers are read and no fingerprinting is performed.
  • Reloading or leaving the page discards the session completely.

Troubleshooting

If the test does not behave as expected

Nothing is registering

Make sure you pressed “Start mouse test” and that the pointer is inside the test area. Events outside the area are not recorded.

Side buttons do nothing

Vendor software or the operating system may have assigned them to another action. Check your mouse software, or try another browser.

The right-click menu still appears

The menu is only disabled inside the test area while listening. Some browser extensions or system settings can override this.

A button looks stuck as pressed

This usually means a release event was missed. Switching tab or window clears it automatically; Reset also clears it.

Horizontal scroll is never shown

Many mice have no horizontal wheel or tilt. On some systems Shift + wheel scrolls sideways, which the test will report.

Movement looks jumpy

Check the surface, clean the sensor and try a different USB port or fresh batteries. Background load can also delay event delivery.

Factors

Common problems this test can and cannot show

Some mouse faults show up clearly in browser events; others cannot be seen from a web page at all.

Unwanted double-clicks

A single click that registers as a double-click can indicate a worn switch. Repeat the test several times and confirm it elsewhere before deciding.

Button not responding

A button that never appears may be failing, disabled by software or remapped. The page can only show that no event arrived.

Wheel skipping direction

A wheel that sometimes reports the opposite direction shows up in the up/down counts. It can be caused by dust or a worn encoder.

Drag that releases early

Hold the left button and watch its state. If it flips to released while you are still holding, the switch may be making poor contact.

Sensor precision

Exact DPI, polling rate and sensor accuracy cannot be measured from browser events because movement is already processed by the system.

Wireless dropouts

Gaps in movement can come from interference or low batteries. The dot only shows what arrived, not why something was missing.

FAQ

Frequently asked questions

How do I test my mouse buttons?
Press “Start mouse test”, then click each button inside the test area. Every button that produces an event is marked as detected, shows as pressed while you hold it, and counts a click when you release it.
Can this test tell if my mouse double-clicks by itself?
It shows every double-click the browser reports and the time between its two presses. If single clicks keep appearing as double-clicks, that is a reason to investigate, but confirm it with repeated tests and another application or mouse before treating it as a fault.
Why don't my side buttons show up?
Extra buttons are often handled by drivers, vendor software or the operating system before the browser sees them, and some are not mapped to any browser event. Not seeing them here does not prove they are broken.
Why can I right-click without a menu appearing?
While the test is listening, the context menu is disabled only inside the test area so the right button can be tested. Everywhere else on the page it works as normal.
What do the wheel delta numbers mean?
They are the raw deltaX and deltaY values the browser reported for the last wheel event. They are not a hardware-standard unit and vary between mice, browsers and scroll settings, so the test relies on direction rather than size.
Does this measure mouse DPI or polling rate?
No. Pointer movement reaches the browser after acceleration and scaling, so raw DPI and polling rate cannot be measured reliably from a web page. The test only confirms that movement arrives.
Does it work with a touchpad?
Partly. Clicks and movement usually register, but touchpads translate gestures, taps and two-finger scrolling differently from a physical mouse, so results are not directly comparable.
Is anything recorded or uploaded?
No. Events are processed in your browser only while the test is running. Nothing is saved or sent anywhere, and leaving the page discards the session.

Found an issue with this test? Report it.