New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 754166 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Keyup events are not executed properly

Reported by steffenf...@gmail.com, Aug 10 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.78 Safari/537.36

Steps to reproduce the problem:
1. Register an event listener for keydown and keyup for the shift key
2. Press shift
3. Keyup event will never be executed

var shiftDown = false;
var setShiftDown = function(event){
    if(event.keyCode === 16 || event.charCode === 16){
        window.shiftDown = true;
    }
};

var setShiftUp = function(event){
    if(event.keyCode === 16 || event.charCode === 16){
        window.shiftDown = false;
    }
};

window.addEventListener? document.addEventListener('keydown', setShiftDown) : document.attachEvent('keydown', setShiftDown);
window.addEventListener? document.addEventListener('keyup', setShiftUp) : document.attachEvent('keyup', setShiftUp);

setInterval(() => console.log(shiftDown), 1000);

What is the expected behavior?

What went wrong?
This occurs in Chrome as well as in Chromium. Might be related to another library? And it doesn't occur on macOS. 

Did this work before? Yes 

Chrome version: 60.0.3112.90  Channel: stable
OS Version: Arch Linux
Flash Version:
 
Cc: susanjuniab@chromium.org
Labels: Needs-Triage-M60 Needs-Feedback
steffenflor@ Thank you for the issue.

Tested the issue on Ubuntu 14.04, Windows 7  and Mac OS 10.12.6 with latest stable 60.0.3112.90 and Canary 62.0.3182.0 with the below steps.

1. Launched Chrome and opened Devtools.
2. Clicked on Console and executed the given code.

Please find the attached screen cast and confirm if anything is missed here.
Also please provide screen cast for the better understanding of the issue.

Thanks..
754166.webm
2.4 MB View Download
Thanks for your feedback. As I said in my original post, the issue might also be related to a recent library update rather than a Chrome update. I'm not really sure. Which library could this be related to? You can find a screen cast of the issue I'm having attached to this post. 
Screencast from 11.08.2017 13:52:26.webm
411 KB View Download
Project Member

Comment 3 by sheriffbot@chromium.org, Aug 11 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "susanjuniab@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by e...@chromium.org, Aug 11 2017

Status: WontFix (was: Unconfirmed)
Unable to reproduce, might be another library that intercepts the events. Try disabling the other ones and see if that helps.

Sign in to add a comment