… 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.

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!!

as noted in the onscreen commentary. I have not been able to reproduce this problem in Chrome, Opera, Firefox, or IE 11.

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.

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

Suggesting a root cause

Help make the web just work! Identifying a root cause helps us resolve issues more quickly. If you have a theory for the root cause or have identified and reduced a reproducible bug, include a description and any relevant code or URLs in your comment and mark it as a root cause suggestion. Our engineers will take a look and update the bug with the results of our investigation.