Issue metadata
Sign in to add a comment
|
onkeyup is not getting triggered after coming back to the tab
Reported by
himanshu...@pearson.com,
Jan 30 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: Points to keep in mind. - i have used windows 7 machine - Print screen key code: 44 Step: Open the html on the given version of chrome 1. Hit print screen key and check the keyup text(not updated) 2. Hit any other key(A-Z or 1-0), check the keydown and keyup text(it's updated with keycode) 3. Now again hit print screen key.(the keyup text is update with key code as 44). 4. Repeat step 2. 5. Trigger a blur event by switch tab or hitting the URL address bar or going out of the current tab and come back again on the same tab. 6. After coming back Hit the print screen key again (the keyup is not updated) 7. Now repeat step 2, and hit print screen key. (the keyup text is updated) What is the expected behavior? The printscreen key should be updated on every keyup. Irrespective of switching tabs or hitting the URL address bar. What went wrong? Not sure, the same html works fine in Chrome 55. Did this work before? Yes 55.0.2883.87 m Chrome version: 56.0.2924.76 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 24.0 r0
,
Jan 30 2017
Bisect: 430936 (good) - 430945 (bad), 56.0.2915.0 https://chromium.googlesource.com/chromium/src/+log/e17b8960..6573d11c?pretty=fuller Suspecting r430939 "Suppress KeyUp events after PreHandleKeyboardEvent consumes RawKeyDown" - see issue 654140 .
,
Jan 30 2017
,
Jan 31 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by tkent@chromium.org
, Jan 30 2017