Touchpad Test

Run one focused browser-local touchpad diagnostic: trace movement, verify clicks and drag, inspect two-axis scrolling and pinch-like signals, compare repeated sessions, and keep browser limits explicit.

browser-local touchpad diagnostic

Touchpad Test — trace what the browser actually receives

Move, click, drag and scroll in one focused surface. See gesture evidence, pointer cadence, movement coverage and issue candidates without pretending a web page can read the touchpad sensor grid directly.

local · no upload · no signup

0/8 core browser-visible actions observed0.0s

0Movement events

0 pxPointer path

0/12Surface zones reached

0Max active pointers

0/0Primary / secondary

0/0Vertical / horizontal scroll

0Pinch-like Ctrl+wheel

—P95 pointer interval

0Large-step candidates

Live diagnostic surface

All-round: move through the grid, click, drag, then try vertical/horizontal two-finger scroll and pinch.

Core action checklist

○Movement

○Primary click / tap result

○Secondary click

○Double click

○Click-drag

○Vertical scroll

○Horizontal scroll

○Pinch-like signal

Browser capability evidence

Session interpretation

Start a session to build browser-visible evidence.

Truth boundary: browsers often expose a laptop touchpad as one mouse-like pointer plus wheel events. Multi-finger OS gestures may be intercepted before the page sees them. The 12-zone grid measures movement across this browser surface; it is not a physical sensor-grid dead-zone map.

Recent event inspector

No events yet.

Compare with a saved summary

Save one compact run, change one condition, then retest.

Local repeat checks

Only summary metrics are stored locally. Raw pointer positions, event history and click timing are not saved in local history.

Ready. Nothing leaves this browser tab unless you explicitly export it.

How to test a touchpad without overclaiming what a browser can see

Movement trails are browser coordinates

Use the 12-zone grid to check whether you can move predictably across the test surface and to spot obvious stalls or jumps. Cursor coordinates are not a calibrated map of the physical touchpad sensor, so this page does not label a specific physical square as “dead.”

Tap-to-click and physical click can look identical

A browser usually receives the resulting click, not the mechanism that produced it. Primary and secondary counts confirm the browser-visible action, but they cannot certify whether the click came from tapping, a diving-board switch or a haptic mechanism.

Two-finger scroll is usually WheelEvent evidence

Vertical and horizontal wheel deltas are useful for testing scroll behavior. The browser normally cannot prove whether those deltas came from a touchpad, mouse wheel or another pointing device, so disconnect an external mouse when isolating a laptop pad.

Pinch may appear as Ctrl+wheel — or not at all

Some desktop browsers expose pinch-to-zoom as wheel events with Ctrl held. Other operating-system gestures are reserved before the page receives them. “Not seen” is therefore a browser-visible result, not proof that the hardware lacks pinch support.

Repeat one gesture at a time

For intermittent problems, compare deliberate tracking, click/drag and scroll sessions separately. Change only one thing — browser, driver setting, power state or external mouse — before repeating the same guided check.

Use lower-level tools for hardware certification

This page cannot read raw capacitance, firmware scan rate, palm-rejection internals or USB/Bluetooth transport timing. Use vendor diagnostics or service tools when you need electrical or firmware-level proof.