Switching between fullscreen Chrome triggers repeated keypresses
Reported by
ymin...@gmail.com,
Apr 5 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36 Steps to reproduce the problem: 1. Open two full-screen chrome windows on a mac, with an empty screen between them. 2. Start at one chrome, Ctrl-arrow to the middle window, lift your hands off the keys and wait a moment. Then Ctrl-arrow to the other Chrome window. 3. hit a key What is the expected behavior? The key press should be registered once What went wrong? Instead, it's registered over and over in a seemingly infinite loop, only ended when you click with the mouse. If you hit other keys, they get added to the repeating cycle. You can end up with 2-3 keys repeating in a loop, amazingly enough. Did this work before? N/A Chrome version: 57.0.2987.110 Channel: n/a OS Version: OS X 10.12.3 Flash Version: Now that I have the replication mechanism up, it's surprisingly repeatable on my fully-up-to-date mac. It also works on an incognito window, so I suspect it's not related to extensions.
,
Apr 6 2017
Can't repro with 10.11. Perhaps a 10.12 issue? Can someone with 10.12 confirm?
,
Apr 10 2017
I'm happy to provide more information on this if it would be helpful. It really is a pretty frustrating bug, though in the meantime I've worked around it by never full-screening my chrome...
,
Apr 11 2017
I couldn't repro this in 10.12. Does this happen with Safari as well? It seems like a macOS bug.
,
Apr 12 2017
I just tried this again with Safari, and could not reproduce, but the reproduction I described earlier continues to work just fine with Chrome. It's worth noting that the reproduction is weirdly brittle. I hit control-arrow to switch to the middle screen, lift my hands off of the control, and press control-arrow again, and then I see the problem. If I keep my finger on control the entire time, then the problem doesn't occur. Maybe also worth noting: I had this on my old laptop, and switched to a new one, and the problem re-occurred. So, to the degree that this is specific to my setup, it doesn't seem to be specific to the hardware.
,
Apr 12 2017
Thank you for providing more feedback. Adding requester "tapted@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
,
Apr 12 2017
Also, I just tried it on a guest account, using a not-logged-in-chrome, so it's hard to imagine that any user-level settings cause the issue.
,
Apr 25 2017
,
Apr 25 2017
,
Oct 8 2017
Any progress on this one? I still see it with Chrome 61.0.3163.100 and OS X Sierra 10.12.6.
,
Oct 15 2017
I just upgraded to High Sierra, and can't reproduce the problem anymore, FWIW.
,
Aug 27
,
Nov 20
*** UI Mass Triage*** Closing this issue as the issue is not reproduced any more as per C#11. yminsky@ -- Request you to file a new issue if the issue is still reproduced on the latest Chrome versions. Thanks! |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by nyerramilli@chromium.org
, Apr 5 2017