Two mappings on one device scramble direction
Aliases: scroll direction clash · mixed mapping · scroll inversion
What it is
A laptop with both a trackpad and a mouse, a convertible switching tablet and desktop modes, a browser stacking touch scrolling on a custom wheel handler: both direction mappings live on one machine. People cannot lock a frame by saying “this is a touchscreen” or “this is a PC”; the first scroll is a coin toss. The scramble is at the channel switch, not because either mapping is unusable alone.
Why it happens
A reference frame calibrated on one channel migrates briefly to the next. Someone who just pulled content down with a finger expects the wheel to continue that way, but the wheel may still be viewport-centric. The reverse calibration also holds. An app that inverts wheel while leaving touch to the system keeps two signs in one window. Embedded iframes, map SDKs, and game viewports often each write their own, so even one channel can reverse across child views. The error feels like “sometimes it works,” and is hard to attribute to mapping.
Studying it
In one session, alternate trackpad and wheel, or touch and pen, and log the first direction error after each switch. Factors include the system natural-scrolling switch and whether the app intercepts the wheel. Split errors into “first notch after a switch” versus “steady use”—only the former prices coexistence. Channel identity must be in the log, or the pattern looks like noise.
Where it stops holding
A desktop with one pointing device, or a phone that is only touch, has no coexistence problem. If the user sets every device to the same model (all natural or all traditional), the clash dies. Remote desktop and VMs can multiply host and guest settings into a double inversion that happens to look correct—an uglier special case. Mixed-mapping scramble is not a velocity threshold or a direction lock.
Applying it
- Do not rewrite system wheel direction inside the app; let touch and wheel follow the OS.
- Audit third-party embedded scrollers for a second inversion of the wheel.
- On a convertible, go touch → mouse → touch and do one targeting task each time; a reversed first move after every switch is coexistence, not “lack of skill.”
Related
- Same group: C3.22.1 Moving the content and moving the viewport are opposite models · C3.22.2 Touch defaults to moving content, wheels to moving the viewport
- Adjacent: C1.16 Trackpads and indirect touch · C1.11 Scroll wheels and inertial scrolling
- Search:
scroll inversion·mixed mapping·natural scrolling