Edge does not fire wheel events when scrolling using the 2-finger scroll gesture on a Precision Touchpad

Issue #7134034 • Assigned to Matt R.


Bryan C.
Apr 6, 2016
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Found in build #
Reported by 27 people

Sign in to watch or report this issue.

Steps to reproduce

To Reproduce:

  1. Use a Win10 device with a precision touchpad (Ex: Surface Pro 3/4/Book)
  2. Use this jsfiddle: https://jsfiddle.net/0z8mvewo/
  3. Try to scroll using the 2-finger scroll gesture.
  4. Edge just scrolls the page instead of firing the Wheel event as expected.
    Try the same jsfiddle in any other Browser… and the event fires as expected.
    This works properly in Chrome and Firefox. Edge also properly fires wheel events for 2-finger scroll gestures on non-precision touchpads (ex: Synaptics touchpads).
    There is NO WORK AROUND until this is fixed as there isn’t even a proprietary Edge-Only event to hook into to prevent the default behavior.
    I Need You to Feel My Pain!
    I’ve been told by multiple Edge PMs that the goal is to create a new standard for precision touchpad gestures. That sounds like a good goal, but as it has now been over 2 years and no progress has been made, we really need the expected wheel event as a stop-gap until that can be accomplished (like every other browser has done).
    Seeing as 2-finger scrolling has been the standard scroll-wheel gesture for trackpads for close to a decade now, it’s very frustrating that this bug has been ignored for so long (I first reported in the IE days, then again in the Spartan days, and now we’re a full year into the Edge days… still no plans to fix).
    Others Who Are Feeling the Pain:
  • This breaks EVERY web experience that relies on wheel events
  • Web GL Engines & Games like Unity
  • Custom cross-platform touch-scroller shims like iScroll
  • Windows 10 apps built on Edge like Flipboard
  • Wheel-based zooming on Bing Maps or Google Maps
  • And obviously, some of my own products
    Waiting for a New Standard Doesn’t Give Me Hope:
    As I’ve said, this has been a pain point I’ve been reporting to Edge PMs for years now so I know you know of it. I wanted to file an official bug so that I can track progress, and hopefully convince you it’s worth fixing before you try to create an entirely new standard for precision touchpads…
    The thing is, a new standard for precision touchpads is just not something any other platform, or even browser, needs. There is no motivation to create a new standard for it outside of Windows 10 and Edge. Every other browser solved the problem by simply firing the wheel event as expected. Why not just do the same?
    Please. And Thank You!


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Rick J.”

    • The platform status page shows this as working. It’s not.


    • I can reproduce it :)

    • Can reproduce!

    • Also able to reproduce; totally destroys scrolling in many web-based text/code editors such as Ace.

    • Sure enough… this breaks ACE too. To verify, just navigate here: https://ace.c9.io/#nav=about and add a bunch of new lines to the code editor until the scroll bar appears. Won’t let you scroll with the precision touchpad.

      This effectively breaks code editing on:

    • This also breaks the new Microsoft CaptionBot.ai site, which lets you scroll through images to try with your mouse wheel… but it doesn’t work in Edge on Surface devices with Precision Touchpads because of this bug.

      To replicate:

      • Browse to the CaptionBot.ai website
      • Point your mouse over the strip of images
      • Try to scroll through them with the 2-finger gesture on a Precision Touchpad
    • Microsoft Edge Team

      Changed Assigned To from “Rick J.” to “Ibrahim O.”

      Changed Assigned To to “Rick J.”

    • Also doesn’t work on a single page scroll plugin like http://alvarotrigo.com/fullPage/

    • Microsoft Edge Team

      Changed Assigned To to “Sermet I.”

      Changed Assigned To from “Sermet I.” to “Andrew B.”

      Changed Assigned To from “Andrew B.” to “Matt R.”

    • This is still broken in the new Edge Build in Win10 14332.

    • This is still broken in the new Edge Build in Win10 14342.

    • So the behavior seems to be starting to change in Build 14352!

      It now seems to fire the wheel event… But ONLY if I scroll UP with a quick 2-finger swipe, and only AFTER I’ve released and the momentum from my swipe takes over… The fired event however ignores the event.preventDefault(); and event.stopPropagation(); calls, resulting in the page’s normal scroll behavior still happening.

      Soo… very happy to see some progress! Hoping this wasn’t an accident but is a sign that a true fix is in the works. Would love to see confirmation from one of you lovely Edge Engineers on this issue.

    • Still broken in 14361

    • Seeing some new progress in 14366. Now if the main scroll bar is at its limit, the wheel event fires… However it still ignores event.preventDefault(), resulting in the main window scroll bar handling scroll when ever it isn’t at the end of the direction you’re scrolling in.

    • A little regression in build 14376. I can still get the wheel event to fire, but only if I swipe 2 fingers to scroll very quickly again and again and again when at the upper edge of the window’s scroll bar. Still ignores event.preventDefault.

      Still hoping a fix for this can make it into the anniversary update 🤞🤞

    • Seconding that sentiment, for what it’s worth.

    • 14388 brings us back to the way it was working in 14366. Seems we just need it to be able to fire the event even if the outer page is not at the scroll limit, and to properly respect event.preventDefault(). Still crossing my fingers for a fix by 8/2!

    • No changes in 14390 and 14393 it seems. 2 weeks & a day 'till launch. I’ve got a case of beer with your name on it if you can fix this before the 1607 launch, Matt!

    • Damn… 14393.5 (the RS1 “Anniversary Update” RTM?) still doesn’t handle precision touchpads like any other touchpad. Would love to see a fix for this make it out in a patch before RS2.

    • Still a problem in 14393.51

    • Still a problem in 14393.82

    • lol, no wonder most have moved on to browsers that just work. Seriously Microsoft? This is core functionality.

    • Still a problem in 14393.105. Too bad so many sites are broken on Microsoft’s own hardware and software as a result of this bug, seeing as all Surfaces released in the past 3 years shipped with precision touchpads. Too bad Microsoft continues to deprioritize this issue even though every single other browser has solved it.

      At least now that Chrome 53 fixed all the battery and performance issues Chrome had, users have a great alternative while MS continues to ignore this critical bug.

    • What is your ETA?

    • Same problem in 1493.187.

    • Also posted to the user voice page where it’s now the 2nd hottest item on the list. Please please please just fix this!


    • Threw my 3 votes at that. I’d vote every point I have if I could. I’d really love to use Edge as a primary browser but given that it doesn’t work with so many modern usecases that involve scrolling, I’m stuck opening a second browser and optimizing my products for other them instead. The fact that we got an extension system before we got functional scrolling is a bit baffling.

    • Microsoft Edge Team

      Changed Title from “Edge does not fire wheel events when scrolling using the 2-finger scroll gesture on a Precision Touchpad” to “Edge does not fire wheel events when scrolling using the 2-finger scroll gesture on a Precision Touchpad”

    • Updating title since the comments have pushed the info regarding it impacting surfacebook and other precision touchpads down a bit.

    • Looks like this bug may also be breaking scrolling in the “Announcements” section of the Windows 10 Feedback Hub… assuming this app was built with HTML/CSS. Scrolling with a mouse wheel works fine when the pointer is over the content of an announcement, but does not work if you use a precision trackpad unless you move your cursor to the far right (where it’s not over the web view that shows the “Announcement” article contents).

    • Still broken in 14971. Blows my mind that you can build new support for Web VR but STILL can’t fire the standard wheel event…

    • Ridiculous that this problem still hasn’t been addressed or acknowledge. It puts a dent on the Microsoft effort for good scrolling on the windows platform. Still hasn’t been fixed on current windows release for Surface Pro 3

    • How can you not have a simple thing like scroll wheel support for trackpads on Edge? I would’ve actually used Edge if scrolling didn’t cause all kinds of havoc through my trackpad.

    • Still broken in 14986. How many years can a feature that’s supposedly supported according to your web platform status page go broken? Nobody at Microsoft cares. That’s clear now. Nobody cares.

    • Absolutely ridiculous. I’d love to tell people that Edge is decent, but I’m definitely not sticking up for a browser that doesn’t scroll correctly on MS’ own flagship laptop. How this issue still exists is completely baffling to me.

    • This is indeed getting ridiculous. What are we supposed to to ? Display a modal telling the user that our web app does not support Edge ? Your problem Microsoft.

    • Ok, Edge PMs… You’ve had years to fix this while it was only affecting Microsoft’s own hardware. Now Lenovo is putting precision touchpads in all their new laptops. Time to get your shit together AND FIX THIS!


    • STILL broken in build 15002.

      …And while I can use my mouse wheel to vertically scroll to make the new tab preview slide left and right, the precision trackpad requires me to go side-to-side. Related?

    • Still broken in 15031

    • Still broken in 15048

    • This bug also appears to affect the on-screen touchpad coming in the Creator’s Update (which presumably uses the same internal APIs as the Precision Touchpad). I’ve opened another bug for this one here:


    • That’s hilariously awful how a known issue cannot be fixed by Microsoft even in insider builds for 2 years…

    • Whenever a change log comes out and I read through the new features and fixes I have to laugh at the decision-making process knowing that this is still open.

    • Makes you wonder if “Matt R.” still works for MS. Or if MS developers actually use their own products.

    • Hey look… an official Edge Blog post claiming “wheel” event support in Edge. WT actual F:


    • Still broken in 15061

    • One of these days this bug will not longer drive me insane.

      Because I’ll be dead from old age.

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

    Sign in