Skip to content

Touchscreen and multi-touch test

Verify screen touch sensitivity across every corner and count simultaneous touch points locally.

Drag or tap across every zone with one or multiple fingers

How to use Touchscreen test

  1. Start in Grid coverage mode. Swipe steadily across the 120-cell surface horizontally and vertically to light up every sector and uncover unresponsive screen strips.
  2. Switch to Fullscreen test for edge inspection. Expand the canvas over your browser bars to test outer corners and bezel boundaries, then select Exit fullscreen when done.
  3. Verify multi-finger tracking under Freehand multi-touch. Place two to ten fingers on the pad simultaneously and watch Active touches, Max multi-touch, and Live pointer coordinates update.
  4. Reset between passes. Select Clear canvas or Clear inside fullscreen to wipe colored cells, trails, and contact counters before testing another zone.

Your camera, microphone and recordings stay on this device. Nothing is uploaded or streamed anywhere.

How does the 120-cell touchscreen test locate dead zones?

Swiping across the pad divides your canvas width and height into 10 columns by 12 rows, lighting each visited square out of 120 cells and calculating live percentage coverage. CSS touch-action: none locks browser scrolling so this digitizer dead zone test maps every millimeter accurately without uploading coordinates.

Sweeping the 10 × 12 grid coverage matrix

Every pointerdown and pointermove contact passes local (x, y) offsets through computeTouchCellIndex, mapping horizontal 0 to width and vertical 0 to height coordinates onto grid indices 0 through 119. Once a square lights green, Grid coverage in Touchscreen status increments both the visited fraction (visited/120) and the rounded completion percentage.

Capacitive touch panels use transparent indium tin oxide (ITO) electrodes laminated beneath the glass. When a drop disconnects a sense trace, dragging across the glass leaves an entire horizontal or vertical row unlit while pixels underneath still light normally. Pair that finding to inspect the underlying LCD panel for dead cells when checking screen damage.

Unified Pointer Events for touch, pen, and mouse

Rather than splitting touch and mouse logic, the interactive surface binds pointerdown, pointermove, pointerup, and pointercancel handlers under W3C Pointer Events Level 3. Calling setPointerCapture(e.pointerId) keeps fast edge swipes locked to the surface even if a finger briefly slips toward the bezel.

Styluses and desktop peripherals work on the same grid without special mode toggles. Moving a mouse without pressing a button (e.buttons === 0) is ignored so accidental cursor hover never paints squares, while touch contacts lacking hardware force sensors fall back cleanly to 0.50 pressure in Live pointer coordinates.

Multi-touch tracking, SVG trails, and live coordinates

Selecting Freehand multi-touch hides the 120-cell grid overlay so SVG rings, colored finger trails, and Live pointer coordinates remain legible during multi-finger pinches and drags. The sidebar records Active touches, Max multi-touch, and Contacts logged simultaneously in tab memory.

Comparing Pointer Events vs Touch Events finger caps

Mobile browsers historically exposed multi-finger coordinates through TouchList arrays defined by the W3C Touch Events Specification. Modern Pointer Events assign each contact a numeric pointerId and pointerType (touch, pen, or mouse), rotating across 10 distinct stroke colors so overlapping paths stay visually distinct.

Even when a capacitive controller supports 10-point hardware tracking, mobile operating systems intercept specific multi-finger patterns before any browser event fires. Three-finger swipes on many Android builds capture screenshots, while four-finger or five-finger pinches on iPadOS trigger app-switching animations outside the browser’s control.

Decimating freehand strokes and active cursor rings

To keep 120 Hz touch displays responsive without bloating SVG DOM nodes, onPointerMove computes Euclidean distance from the last recorded trail point and only appends a vertex once movement reaches 3 px. Each active contact retains up to 81 recent points while lifting a finger archives up to 25 completed strokes behind semi-transparent ink.

Active fingers draw a crisp 18 px radius circle (22 px in fullscreen) centered at integer (X, Y) coordinates. Alongside finger diagnostics on convertible tablets or gaming handhelds, you can open the Gamepad and controller tester to verify attached thumbsticks and shoulder triggers in the same browser session.

Fullscreen touch bezel inspection across phones and tablets

Embedded web cards leave roughly 10% to 20% of a phone screen outside the touch pad because address bars, bookmarks, and navigation buttons frame the page. Clicking Fullscreen test expands the interactive surface across the entire display so edge swipe zones and curved bezels get direct coverage.

Using requestFullscreen with fixed-viewport fallback

Activating Fullscreen test invokes Element.requestFullscreen() as specified in the W3C Fullscreen API Specification. On mobile browsers that restrict programmatic fullscreen on non-video elements, including iOS Safari, the component falls back to a fixed inset-0 z-50 viewport overlay covering every reachable CSS pixel.

A slim top bar inside the fullscreen dialog shows live percentage coverage, visited/120 cell tally, and Max fingers, paired with Clear and Exit fullscreen buttons. Keeping both modes aligned ensures a dead corner spotted near a notification shade or home bar stays reproducible after resizing.

Comparing grid coverage and freehand test modes

Choosing the right view depends on whether the goal is finding dead digitizer strips, testing palm rejection, or checking multi-finger chords. Switching between Grid coverage and Freehand multi-touch preserves existing visited cells and max-finger records until you select Clear canvas.

Diagnostic mode Canvas behavior Key sidebar or header metric Primary hardware issue exposed
Grid coverage Paints 10 × 12 matrix cells green Grid coverage (visited/120 and %) Dead ITO rows, missed corners, edge drop-offs
Freehand multi-touch Hides grid; emphasizes trails and rings Active touches and Max multi-touch Multi-finger drop limits and pointer ID merging
Fullscreen test Expands pad over browser bars via dialog Top-bar Coverage: % and Max fingers Unresponsive top notification strip or bottom bezel
Live pointer coordinates Lists active contacts during touch down ID, pointerType, X, Y, and P pressure Phantom coordinate jumps and stylus tilt/force gaps

Touchscreen laptops sometimes experience cursor jumps caused by an external mouse or built-in clickpad rather than the glass panel itself. Run a primary mouse switch bounce diagnostic alongside your finger sweep to separate switch chatter from digitizer faults.

Diagnosing ghost touches, palm rejection, and glass guards

Ghost touches occur when the digitizer fires spurious pointerdown coordinates while no hand touches the glass. Leaving the pad untouched for 15 seconds after pressing Clear canvas makes phantom taps obvious immediately because Contacts logged climbs above 0 on its own. Rest your wrist lightly on a corner while drawing with an active pen to verify hardware palm rejection ignores broad skin contact.

  • Cracked screen protectors: Air gaps under chipped tempered glass trap moisture or alter local capacitance, mimicking dead touch rows until peeled off.
  • Ungrounded power adapters: Cheap third-party USB chargers inject 50 Hz or 60 Hz common-mode electrical noise into capacitive sensing electrodes; unplug the charger and re-test on battery power.
  • External pointer overlap: On Windows 2-in-1 laptops, an external wireless receiver can inject jittery movement alongside touch; measure USB mouse report intervals beside trackpads with the mouse unplugged vs connected to isolate the culprit.

Tip: Wipe oily smudges off the glass and test on battery power first before assuming an unresponsive corner or phantom tap requires a full display assembly replacement.

Questions

How do I find a dead strip on a phone or tablet digitizer?

Choose Grid coverage and expand Fullscreen test, then drag one finger slowly row by row and column by column. Damaged capacitive sense lines leave a straight uncolored stripe across cells even when your finger sweeps directly over them.

Why does fullscreen mode help inspect screen edges and corners?

Embedded cards stop short of device edges because address bars and navigation frames consume outer pixels. Entering Fullscreen test stretches the touch surface across the entire viewport so bezel corners and curved glass edges receive direct taps.

How many simultaneous multi-touch fingers can the canvas track?

The browser canvas imposes no fixed finger limit and cycles through 10 distinct ring colors per active pointerId. Most modern capacitive phone and tablet digitizers report up to 10 simultaneous touches once operating system gestures are avoided.

Why do four-finger or five-finger swipes trigger OS gestures?

Android and iPadOS intercept three-finger, four-finger, or five-finger pinches at the window manager level for screenshots and app switching. Testing inside Fullscreen test or pinning the app helps bypass some bars, though OS-reserved gestures still take precedence.

Does the touch canvas also support stylus pressure and desktop mice?

Yes. Because the pad listens to unified W3C Pointer Events, Apple Pencil, Wacom styluses, trackpads, and mouse clicks all draw rings and update Live pointer coordinates, displaying normalized P pressure values from 0.00 to 1.00.

What causes phantom ghost touches when no finger is on the glass?

Moisture, static buildup from ungrounded third-party chargers, or micro-fractures lifting a capacitive glass layer can trigger erratic false touches. Remove cracked tempered glass protectors and unplug cables first to verify whether the underlying digitizer stays calm.

Updated