- Fingers now
- 0
- Peak at once
- 0
This browser
Pointer Events work with a mouse or a touch screen. Trust the detection on this page, not a version table.
- Pointer Events checking
- navigator.maxTouchPoints checking
Touch screen test in this tab: multi-touch trails, a dead-spot grid, and browser event sample rate. Test touch screen response with a finger or a mouse.
Nothing is uploaded. Pointer events are handled in this tab and never sent anywhere.
Pointer Events work with a mouse or a touch screen. Trust the detection on this page, not a version table.
A touch screen test that stays in this tab: a multi touch test online with one colour per finger and a trail, a sample-rate readout, and a touch screen dead spot test on a grid. Nothing is uploaded. Test touch screen response with a mouse or a finger — this page uses Pointer Events (pointerdown / pointermove / pointerup / pointercancel), not the older Touch Events API.
Each contact keeps one colour until it lifts. The live count is how many contacts are down right now; the peak is the highest simultaneous count this session. pointercancel is treated as a lift so a system gesture cannot leave a ghost finger on the pad.
The hertz figure is the browser event sample rate, not the panel's hardware touch rate. Browsers coalesce pointer events, so the number is lower than the datasheet. Treat it as how often this tab is hearing moves, not as a factory spec.
The grid only records that a cell received a touch event. A missed cell can be a fast swipe that never crossed it, a lifted finger, or a real dead zone. It is not a panel-level stuck-pixel or digitizer inspection. Reset and try a slower pass before you blame the glass.
No. It is the browser event sample rate. The browser merges pointer events, so the hertz you see is lower than the panel spec. Use it to compare how often this tab is getting moves, not to check a datasheet.
Not by itself. The grid only proves a cell received a touch event. A fast swipe, a lifted finger, or a real dead zone can all leave a cell empty. Reset and draw more slowly before you treat a gap as hardware.
Yes. A mouse still sends pointer events, so single-point trails, sample rate, and the dead-spot grid all work. This device's navigator.maxTouchPoints is shown on the page; a value of 0 means multi-touch needs a real touch screen.
Any browser that exposes Pointer Events. Detection runs after the page mounts. Treat the detection line on this page as the source of truth, not a version table. About and FAQ render in every browser, including ones that cannot receive pointer events.
No. Pointer coordinates, trails, sample timestamps, and the coverage grid stay in this tab. There is no account and nothing is uploaded.
Dead pixels, backlight bleed, banding, gamma, ghosting, refresh rate.
Buttons, double-click chatter, scroll notches, polling rate.
Pressure curves, tilt angles, barrel twist, and estimated pressure levels.