Start, then hold the primary mouse button and move inside the pad. Release when ready. You will be asked whether that release was intentional.
A canceled or interrupted run does not establish a hardware problem.
What reached the browser
No input observed yet.
0 CSS px of pointer travel observed.
Cannot judge yet
No completed run yet. Untested inputs are not failures.
Observations describe this browser session. They do not certify hardware health. Read the method and next steps →
If a drag lets go before you release
You hold the primary button and move, but the item drops mid-drag. In the browser that is a release (pointerup) or a lost pointer capture arriving while you believe the button is still down. This check needs at least eight CSS pixels of travel, then asks you to confirm whether that release was intentional.
A hardware cause and an ordinary cause look the same
A mid-drag release can come from a switch that is not holding contact, from the pointer leaving the capture area, or from the operating system interrupting the gesture. Confirming whether you meant to release is what separates a reported observation from an ordinary end-of-drag — the tool never guesses your intent for you.
How to read your result
- Not observed: your releases were confirmed intentional in completed runs.
- Needs another check: one run recorded a release you did not intend; repeat it.
- Observed in more than one run: an unintended release repeated in this session under the same steps.
- Cannot judge: too little movement, an interrupted run, or lost pointer capture while the button was held.
What your shareable report shows
Your exported report records whether each release was confirmed intentional, the pointer travel observed, your browser and operating system, and whether the pattern reproduced across runs — enough for a support ticket to see exactly what you did.
If it reproduces, what to do next
- Repeat the hold-and-move in a fresh browser session, then on another surface (mouse versus trackpad) or another computer, using the same deliberate steps.
- Confirm the button is not being intercepted by mouse software, gesture utilities, or an accessibility setting.
- If unintended releases reproduce across sessions and devices, note it with your exported report and check the manufacturer’s warranty or return options. Treat the browser result as evidence, not a hardware verdict.
These steps are general guidance, not a diagnosis. A browser check documents what happened in this session — the manufacturer confirms a physical fault. See the full method → See the open data →
Use a result as a starting point
If an unexpected event repeats, try a fresh browser session and another port or device where practical. Compare the same steps. A result can depend on the browser, operating system, input settings and physical device.
Does this measure hardware latency or polling rate?
No. Browser event delivery is affected by scheduling and input processing. These tools do not certify hardware latency, USB polling rate, DPI accuracy or switch lifespan.
Where do my results go?
The last 30 runs stay in this browser’s local storage. Use the history button to copy a readable report, export JSON or remove them. Raw keyboard and pointer event streams are not sent to a server by this app.