Edge gestures are especially exposed to edge-field distortion

What it is

System back, Control Center, and home-bar swipes treat the screen boundary itself as the onset feature: begin must land in the outermost strip, after which displacement and speed count. Edge-field distortion lives in that same strip—coordinates shoved inward, slid along the bezel, or parallax-shifted on a curve. The recognizer therefore misclassifies more often than an ordinary swipe in the centre: a gesture that should fire is read as in-page scrolling, and one that should not is stolen as a system gesture.

Why it happens

An edge gesture’s first gate is “was onset close enough to the edge?” Distortion reports a truly flush begin as already several pixels into content, the latch fails, the whole gesture is void, and the user thinks back is broken. Conversely, a compensation table that pushes coordinates off-screen can treat a slightly inward begin as flush and steal an in-page horizontal pan. Speed is estimated from the already-distorted point series; along-edge drift injects a fake tangential velocity, so a vertical swipe is read as diagonal and fails. Recognizers also arbitrate against in-page scrolling in the first frames: distortion dirties those directions and makes the window easier to call wrong. Centre swipes have no “must be flush” latch, so the same distortion hurts them far less.

Studying it

Run back, pull-down, and home-bar swipes from the true outer lip and from starts 2–6 mm inward, on flat and curved devices. Independent variables are onset distance from the physical edge, compensation on or off, and whether the page has horizontal scrolling. Dependent measures are recognition success, fraction treated as in-page scroll, latch rejections, and error in the recognised launch direction. Overlay log begin coordinates on a photo of the screen to see “finger on the bezel, system thinks we are already in content.” Cases and films are conditions, because they change the physical edge the gesture depends on.

Where it stops holding

Replacing the edge gesture with an on-screen button or a home-bar capsule removes dependence on the edge field, and this interference vanishes. “Edge gestures” on a trackpad or mouse travel a different coordinate system with no capacitive truncation. A full-screen game stick that happens to be drawn at the side is a flush control, not a system gesture that uses the boundary as onset. Gestures near a foldable’s crease are a different geometry; side-edge distortion does not transfer there.

Applying it

• Set the onset latch from outer-surface measurements, not from a pixel rectangle; remeasure with the target case on, and widen the strip or warn the user if the case raises the physical edge.
• Give back and Control Center a path that does not need to be flush (an on-screen button, an accessibility gesture), especially on badly distorted curved sides.
• QA with both “slide on the bezel” and “slide a few millimetres in,” counting latch rejects and stolen in-page pans separately; do not only swipe the centre.

Related

• Same group: C2.21.1 Incomplete edge electric fields systematically distort touch coordinates · C2.21.2 Flush-to-edge controls hit-test less reliably than center ones · C2.21.3 Curved edges compound optical distortion with incomplete sensing
• Nearby: C3.13 Edge swipe gestures · C3.14 Back gestures
• Search terms: edge gesture · back gesture · edge field