Edge fails sporadically to provide key released event to ProcessingJS environment

Fixed Issue #11752508

Details

Author
Christopher
Created
Apr 21, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14.14393
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

  1. Start Edge
  2. Navigate to https://www.khanacademy.org/computer-programming/demonstrate-keypressed-and-keyreleased-behavior-in-ms-edge/4985002837475328
  3. press the UP arrow key and then release it.
  4. if the shark stops moving then go back to step 3; otherwise, …
  5. … you are seeing the bug!! The shark is moving up and you are not touching the keyboard. It usually does not take more than a few seconds to reproduce.
  6. feel free to uncomment the println statements in the keyPressed and keyReleased functions. You will see that when the problem occurs the "pressed: " statement is printed out but there is no terminating "released: " statement even though no keys are being pressed!!
  7. as noted in the onscreen commentary. I have not been able to reproduce this problem in Chrome, Opera, Firefox, or IE 11.
  8. 'tis very strange indeed.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

      Changed Status to “Fixed”

    • Hello,

      Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge 15063 and is available in our latest Creator’s Update build.

      Best Wishes,
      The MS Edge Team

    • I’m happy to report the Psychic Friends Network is working at Microsoft fixing bugs I hadn’t even reported yet. I have downloaded and installed the Creator’s Update build. The Edge browser now seems to robustly handle the keyboard input reporting needs of ProcessingJS on the KA website.

    • okay, after a while running the updated version of windows 10 build 15063.138 I started seeing display flicker due to the display adapter driver failing which was confirmed by seeing multiple event ID 4101 in the system event log. This problem is due to an incompatible Intel HD graphics 530 driver version 21.20.16.4590 which I previously had to roll back.

      (see Community report
      https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/display-driver-failures-after-windows-update-intel/8c90cba4-4d9d-4d13-8fb4-1d55a1a2801c?tm=1491590026276

      here is the post rollback configuration to working system:
      Dell laptop XPS 15 9550 running Windows 10 Home ver. 1607 build 14393.969
      CPU I7-6700 HQ @ 2.6GHz; RAM 16 GB
      Display 3840x2160 touch panel
      NVidia GeForce GTX 960M driver 21.21.13.7270 dated 8/25/2016
      Intel Adapter HD Graphics 530 driver 20.19.15.4531 dated 9/26/2016 )

      I went to the device manager after installing the Creator’s update build and found that there was no option to roll back the driver!!! So I had to get the driver from Dell. As of now the older driver noted above seems to be working with the Creator’s update build of Windows 10

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

    Sign in