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.
