-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sometimes, the my keys stop getting registered. #23
Comments
pubads.g.doubleclick.net/gampad/ads?ad_rule=0&d_imp=1&gdfp_req=1&impl=ifr&iu=%2F4061%2Fcom.ythome&scp=dc_yt%3D1%26k18%3D1%26k21%3D1%26kage%3D21%26kar%3D3%26kauth%3D1%26kbsg%3DHPUS170408%26kga%3D1001%26kgender%3Dm%26kgg%3D1%26klg%3Den%26kmyd%3Dad_creative_1%26ssl%3D1%26ytdevice%3D1%26ytexp%3D9422596%252C9428398%252C9431012%252C9434289%252C9446054%252C9451825%252C9456628%252C9460350%252C9468270%252C9470024&sz=970x250&ytdevice=1&correlator=7945266235241948 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT |
Above is a the console logs from when my keys stopped working. At the time, I had just added a new hotkey to the extension and had just reloaded it. I am not sure if this what caused the keys to stop working. However, the way that the keys stopped working is clear from the logs. As I was pressing keys, I realized that the hotkey that was being sent over was not being emptied out after it was sent. Rather, whether or not I was pressing the escape key, every keypress appended to the hotkey that was to be sent out and it just kept getting longer and longer (even though it's supposed to empty out after it's been sent). I assume this means that the extension believes that the escape key is being perpetually held down and, while it sends out the hotkey when the escape key is released (which means it does detect the key release), it does not then replace the hotkey with an empty string. |
I tried pressing the escape key a few times (without pressing any other keys) and the long hotkey keeps getting sent, but the hotkey still does not get emptied out. I notice that the same is happening for all of my tabs right now. |
The runtime.connect error suggests the same broken connection problem discussed in #17. If you reload the extension, all currently open tabs will no longer be able to communicate with the background script unless you reload them. But you should no longer have to reload the extension after editing your options since 4cf9271, because #3 is now fixed. If this resolves it, remove the bug and priority label, add WAI, and close. |
I am not sure what causes this, but it doesn't happen often. It just happened when I switched tabs in the rightward direction and came back to my original tab. My keystrokes were not having any effect until I refreshed the page. I believe this may have something to do with the fact that the key release of the escape key is not registered in the original page and it might be causing occasional problems, but I am not sure.
The text was updated successfully, but these errors were encountered: