Pointer input blocked by rendering

Fixed Issue #10007805


George C.
Nov 30, 2016
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

When rendering performance intensive content (like WebGL demos), if the framerate is less than 60fps there will be significant mouse/touch delay.

This is not the case in other browsers running at similar framerates

I’m seeing a good 3 to 4 seconds delay between an interaction and seeing the results - while waiting for the input to be received the application is rendering 10s to 100s of frames, so it’s not a delay in rendering, but a delay in communicating pointer events

This has a major impact on the feel of quality about the browser


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Sermet I.”

      Changed Assigned To to “Rico M.”

    • Significant work has been done in this area however without a specific case I don’t feel comfortable saying it’s “fixed” for you.  Can you give me a specific URL I can control against so I can be sure I’m seeing what you were seeing?


      If it’s any consolation I know exactly what you’re talking about and I do think it’s at least substantially better but that’s not the same as “yup I’m sure I fixed your problem”

    • Microsoft Edge Team

      Changed Status to “Confirmed”

    • Hey Rico

      The URL I was testing was https://threejs.org/examples/#webgl_shaders_tonemapping

      Input delay seems to affect CSS hover as well as canvas mouse/pointer events

      I’m running:
      Microsoft Edge 38.14393.0.0
      Microsoft EdgeHTML 14.14393

      Windows 10 Enterprise
      version: 1607
      OS build: 14393.447

    • Thank you for the URL!


      I’ve got something much more recent version 14985 – something near that version should be in a public flight soon.


      On my system I’m getting nothing like 3-4s delays, while it’s not perfect the delays are now more like 20-30ms (like a frame or two).  My system isn’t so burly that it can do all that webgl and keep up clean so that’s not bad.  Not perfect mind you but hella better.


      Now on a machine with a better GPU that same page is totally crisp – I just used an SP4.


      Any chance you’re getting software rendering on your system?

    • I did some more tests and I can confirm my slower system is using software rendering.  CPU usage for that page is 100%.

    • Microsoft Edge Team

      Changed Status from “Confirmed” to “Fixed”

    • The software rendering problem you may or may not be seeing.  I was seeing it.


      The input delay problem seems not present in builds >= 14993, we did much work in that area.


      Can you advise if you’re doing better when you get the next flight after the new year?


      I’m going to go ahead and marked this “fixed” for now but I’d really appreciate a confirmed kill on this.


      Thank you!

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

    Sign in