Two-finger co-directional motion maps to scrolling, distinguished from pinch by count and relative movement

What it is

A trackpad recognizes two fingers moving roughly together and over similar distances as two-finger scrolling. It distinguishes this from pinch zoom through contact count, change in finger separation, and relative movement: shared translation moves content, while separation change alters scale.

Why it happens

The recognizer continuously estimates shared translation, distance change, and rotation, typically converting each into a strength score and picking whichever category scores highest, and it has to commit to that choice early in the motion. The genuinely hard part is not telling these three kinds of motion apart when they happen alone — it's that in real use they routinely happen together: someone pinches to zoom out while simultaneously panning to look at a new area, a compound motion that is completely ordinary in photo viewers and map apps rather than an edge case for the recognizer. If the recognizer treats "scroll" and "pinch" as mutually exclusive categories that force a single pick, it inevitably has to take a side on this compound motion, and whichever side loses makes the content feel like it is tracking the fingers except that "it won't zoom when it should" or "it won't pan when it should."

Studying it

Perform scrolls and pinches across spacing, speed, angle, and landing order; record classification errors, latency, scroll distance, and recovery. Analyse edge cases: slight opening during a scroll, a temporarily stationary finger, and operation near the trackpad edge. More importantly, construct samples of the "pinch while panning" compound gesture on purpose and analyse them as their own category rather than folding them into either scroll's or pinch's misclassification count, because these samples test whether the recognizer can output two continuous quantities at once, not whether it picks the right one of two exclusive categories.

Where it stops holding

Platform settings can disable, alter, or reserve two-finger gestures, so applications cannot assume uniform devices. Touchscreen devices may interpret the same motion as system navigation; core functions need wheel, keyboard, or visible-control routes.

Applying it

• Distinguish scroll and pinch from relative evidence of shared translation and separation, not count alone, and let both take effect simultaneously as continuous quantities rather than forcing an either-or choice.
• Avoid large content jumps while recognition is unsettled, then keep feedback consistent after lock.
• How to check: replay the recognizer specifically against "pinch while panning" compound motions and verify that both the resulting zoom amount and displacement track sensibly, rather than reporting only a single gesture category's classification accuracy.

Related

• Same group: C1.23.2 Horizontal scrolling usually needs explicit horizontal content or a modifier, otherwise it is ignored · C1.23.3 Trackpad inertial-scroll deceleration shares the perceptual rules of touchscreen inertia · C1.23.4 Misclassifying two-finger scroll as another multitouch gesture abruptly interrupts scrolling
• Nearby: C1.22 Drag thresholds and intent classification · C2 Touch and multitouch
• Search terms: two-finger scroll · pinch · gesture recognition