Over-eager 2-finger swipe back/forward gesture: 2-finger Precision Touchpad scrolling swipes doesn't lock to Y-Axis when scrolled to the top of a page

Issue #7711757

Details

Author
Bryan C.
Created
May 27, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14.14352
Reports
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

Using a precision touchpad to use 2 fingers to scroll up/down a page now results in some confusing jiggling when a page is scrolled to the top as mostly vertical swipes aren’t being locked to the Y-Axis, resulting in the page diagonally shifting while the swipe/forward/back guesture creeps in.

The X / Y Axis locking works well when scrolled down to the middle of a page, only detecting true left/right 2 finger swipes as forward/back gestures, and allowing slightly diagonal up/down 2 finger swipes to only scroll without shifting the page contents from side to side. It’d be great if the same axis locking was in full effect when scrolled to the top of the page too.

Attachments

0 attachments

    Comments and activity

    • Did a little more testing… this is also a problem when scrolled to the bottom of a page.

    • Microsoft Edge Team

      Changed Assigned To to “Ted D.”

    • This is still an annoyance in build 14361

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Assigned To to “Rick J.”

      Changed Assigned To from “Rick J.” to “Li-Hsin H.”

      Changed Status

    • This issue has been resolved External. This means this issue may require a new feature to be implemented or other work that is more significant than a typical bug. You may be able to find more information on this issue by searching for related features on status.microsoftedge.com and uservoice.microsoftedge.com.

    • This is driving me nuts. I use two finger scrolling all the time and now I am regularly losing the page I am due to accidental back/forward swiping. This is especially annoying when doing data entry on a page.

    • Can confirm this is fixed in 14388

    You need to sign in to your Microsoft account to add a comment.

    Sign in