Escape key event is not captured in input elements on OSX |
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 Steps to reproduce the problem: 1. Attach a keydown, keyup, or keypress event handler to an input element. 2. Focus on the input 3. Press the escape key What is the expected behavior? A KeyboardEvent is triggered with keyCode 27, showing that the Escape key was pressed. What went wrong? The text field loses focus and no KeyboardEvent is triggered. This behavior continues even if preventDefault() is called. Did this work before? N/A Chrome version: 63.0.3239.132 Channel: n/a OS Version: OS X 10.13.3 Flash Version: This behavior does not occur in Chrome on Linux. Haven't tested Windows.
,
Feb 16 2018
,
Feb 16 2018
ederby@ - Thanks for filing the issue...!! Could you please provide a sample test file/url to test the issue from TE-end. This will help us in triaging the issue further. Thanks...!!
,
Feb 20 2018
Hi, I can reproduce this issue with this CodePen: https://codepen.io/anon/pen/JpLBgy
,
Feb 20 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 22 2018
I cannot reproduce this on a Mac Book with a touchbar. In chrome 64.0.3282.167 which is the current stable version. I also tried m65 as well. ederby@ does this reproduce in a incognito window? Specifically I'm wondering about any extensions installed. I don't see it change focus when I hit ESC. What IME & keyboard layout are you using?
,
Feb 22 2018
This appears to be an extensions-related issue, as I cannot reproduce in an incognito window. Thanks for your help.
,
Feb 22 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 22 2018
Closing as per it is an extension issue. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by bokan@chromium.org
, Feb 15 2018