touchscreen multitouch test
This page reads touch events inside a dedicated area and shows three point lists at once, along with the maximum number of simultaneous touches your hardware supports. The touch points detected exist only in the memory of this open tab and never travel outside the device.
Since both touches started inside the element, the two lists match in this case; the difference only shows up once a touch lands outside the area.
touches counts both because it looks at the whole screen, but targetTouches counts only the finger sitting over the target element, the clearest proof of the difference between the two lists.
changedTouches shows only the finger that just left, even while another finger keeps touching the screen normally without entering that change list.
Yes, if the device and browser expose touch or pointer input, for example a touchscreen monitor or a 2-in-1 laptop. On a plain mouse you will see pointerType mouse.
touches lists every touch on the entire screen, targetTouches lists only the touches that started inside the observed element, and changedTouches lists only the touches that changed state in that specific event; all three can have different lengths at the same instant.
It is a contact point reported by the panel without the person actually touching the screen, usually caused by electrical interference, moisture on the surface, or a momentary glitch in the touchscreen controller, and it shows up on this page as an extra touch with no visible explanation.
Because mobile browsers reserved about 300ms after a tap to check whether a second zoom tap was coming before firing the click; the CSS touch-action property lets a page tell the browser it already handles gestures on its own, which removes that wait.
navigator.maxTouchPoints reports that limit straight from the panel hardware; this page displays that number, and it is usually 10 on modern smartphones, but it can be much lower on simpler panels or older resistive screens.
Touch points are drawn locally and never leave this tab.