Every touchpad has a blind spot — it just lives at the edges. Drag your finger to a corner and you may notice the cursor hesitates, snaps slightly, or lands a few millimeters off from where you aimed. This is not a driver glitch and it is not wear. It is a fundamental consequence of how capacitive sensors work, and every manufacturer trades off against it differently.
Why edges are harder to measure
A capacitive touchpad works by measuring changes in an electric field across a grid of electrodes. When a finger sits near the center, electrodes on all sides sense the distortion symmetrically, and the firmware can interpolate the finger's centroid very accurately — often to a fraction of an electrode pitch. Near an edge, the geometry breaks: electrodes exist only on one side of the contact, so the field is asymmetric. The firmware receives a lopsided signal and must extrapolate rather than interpolate. Extrapolation is inherently less accurate.
Corners are the worst case. At a corner, two full electrode rows are missing, leaving the sensor with roughly a quarter of its normal surrounding data. The firmware may pull the reported contact inward slightly — a phenomenon sometimes called edge pull-in — because the interpolated centroid drifts toward the denser part of the sensor array.
What the Precision Touchpad specification tolerates
Microsoft's Windows Precision Touchpad requirements acknowledge the physics by setting a relaxed linearity tolerance specifically for the near-edge zone. In the bulk of the surface, a tracked contact must stay within 0.5 mm of its true path. Within 3.5 mm of the physical edge, that tolerance expands to 1.5 mm — three times the allowable error. For edge detection (whether a contact registers at all near the boundary), the spec requires contacts to be reported within 2 mm of the physical edge. A pad that cannot detect a finger 2 mm from the rim fails certification.
In other words, even a fully certified Precision Touchpad is officially permitted to be three times less accurate near the edges than in the center. A non-certified standard touchpad has no such specification at all — linearity near edges is entirely up to the vendor.
How the tester's edge warning connects to this problem
The orange warning border that appears in the test canvas above activates when your pointer comes within 30 pixels of the canvas boundary. This is a deliberate design choice that maps to the real-world edge zone: at typical laptop screen resolutions, 30 CSS pixels corresponds to roughly 5–8 mm of physical touchpad surface — the region where capacitive accuracy starts to degrade and where PTP's looser linearity tolerance kicks in. The warning is not just a UI affordance; it marks the zone where your test results should be interpreted more cautiously.
In practice, this means a dot placed near the canvas edge may not land exactly where the GestureDetector registered the pointer event. The driver may have already shifted the reported coordinate slightly inward before the browser ever received it.

What you can do about edge inaccuracy
Understanding the limitation helps you work around it rather than fight it:
- Map high-precision targets away from edges — small UI controls like close buttons and resize handles typically live at screen edges, but they map to center touchpad coordinates for most cursor movements. Only gestures that start at the physical edge (edge swipes) require edge accuracy.
- Use edge swipes deliberately — on Windows, three-finger swipes for Task View or four-finger swipes for virtual desktops do not need sub-millimeter precision; a wide swipe motion tolerates the edge drift.
- Calibrate your pointer speed — a higher pointer-to-touchpad ratio reduces the effective distance your finger travels before reaching a target, which means you spend less time in the high-error edge zone for typical clicks.
- Test corner taps specifically — if right-click via corner tap feels unreliable, tap the lower-right zone slightly more toward center. On many pads, the click zone for a corner right-click has a physical sweet spot 5–10 mm inside the corner.
One honest limitation of browser-based testing: you can observe the edge warning trigger and compare dot placement at the canvas center versus near the boundary, but the absolute accuracy offset (how many millimeters the reported coordinate drifts from the true contact) is not measurable from a web page. The driver has already processed and potentially corrected the coordinate before the browser receives the pointer event. Firmware-level accuracy testing requires the Windows Hardware Lab Kit touchpad tests, which use mechanical contact probes and hardware timestamps.
Check yourself: try placing taps at each of the four corners of the test canvas above, then compare where the green dots land relative to where you tapped. If corner dots consistently appear slightly inward from the canvas edge, your touchpad's edge pull-in is showing through the driver — a normal physical characteristic, not a defect.