BeanNestTools

Touch coverage check

Trace the screen and see where real touch reaches the browser.

Cover the grid, trace edges and corners, and try several fingers together. Mouse and pen input can preview the surface on desktop, but only browser-reported touch contacts count.

Runs in your browserNo coordinate uploadNo account needed

Touch screen test workspace

StatusReady — touch the test surface when you are ready.Mouse and pen previews are deliberately not counted as touch.
Coverage0%
Cells0 / 96
Active now0
Max together0
Browser max touch points
0
Last input
None yet

“Browser max touch points” is capability context reported by the browser. “Max together” is only the largest number of real touch contacts you actually produced during this session.

How to use it

Check coverage, continuity, then simultaneous contacts.

  1. 01

    Fill the grid

    Drag a finger across the surface. Covered cells stay marked so skipped or difficult areas are easy to revisit.

  2. 02

    Trace edges and corners

    Run a finger close to each bezel edge and through all four corners. Out-of-surface pointer movement is ignored instead of falsely marking the edge.

  3. 03

    Try multiple fingers

    Place two or more fingers down together. Compare Max together with what you intentionally tested; the browser-reported maximum is context, not an automatic pass/fail target.

What the result means

Only real browser-reported touch changes the test result.

Pointer Events identify whether an input came from touch, pen, or mouse. BeanNest updates coverage and simultaneous-contact counts only when the browser labels the pointer as touch. Desktop mouse or pen activity is a visual preview, not touchscreen proof.

Coverage is a browser observation, not hardware certification.

A missed area can be useful troubleshooting evidence, but the web page cannot isolate panel electronics, digitizer firmware, operating-system gesture handling, a damaged protector, or an application-specific issue by itself.

Raw touch coordinates are not retained.

The page keeps only a 96-cell covered/not-covered set and active pointer identifiers in memory. Raw coordinates, traces, pressure, tilt, pointer IDs, and maxTouchPoints are not persisted or sent to analytics.

Why does my mouse move a marker but not increase coverage?

That is intentional. Mouse and pen input are useful for checking that the page renders and responds, but they cannot prove that a physical touchscreen produced a touch event.

What does browser max touch points mean?

It is the maximum simultaneous touch-contact capability the current browser environment reports. It does not mean you have already tested that many contacts, so BeanNest shows it separately from Max together.

Why can the page stop scrolling inside the test area?

The active surface uses browser touch-action rules so drag gestures can reach the diagnostic instead of scrolling the page. That behavior is scoped only to the test surface; normal page controls and content outside it keep normal browser scrolling.

Can automated browser tests prove my touchscreen works?

No. Synthetic events can regression-test BeanNest's logic, but only real touch on your device can provide physical acceptance evidence for your screen.

Keep checking

More device checks

Mouse Test

Check mouse buttons, wheel input, browser double-click events, movement, and hold continuity locally.

Open tool →

Keyboard Test

Check the keyboard events your browser receives, including held keys, modifiers, physical key codes, and repeat state.

Open tool →

Sound Test

Test left and right speaker output, microphone input level, and a short local recording without uploading audio.

Open tool →