Issue metadata
Sign in to add a comment
|
Keydown =, keyup cannot be stopped in contenteditable
Reported by
ilchenea...@gmail.com,
Mar 14 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.146 Safari/537.36 Steps to reproduce the problem: 1. Open test.html 2. focus on content editable area 3. Press backspace/left/right arrow key What is the expected behavior? 4. Those key (backspace left/right arrow key) should not work because their keydown/keyup events has been preventDefault() and stopPropagation() What went wrong? Those key works. Did this work before? Yes Maybe 64 Does this work in other browsers? N/A Chrome version: 65.0.3325.146 Channel: n/a OS Version: OS X 10.13.3 Flash Version:
,
Mar 15 2018
Thanks for filing the issue! Unable to reproduce the issue on reported chrome version 65.0.3325.146 using Mac 10.13.1 with the below mentioned steps. 1. Opened test.html in a new tab 2. Focused on content editable area 3. Pressed backspace, left and right arrow keys We didn't observe any of those keys are working. Attaching the screen cast of the same. @ilchenearly: Could you please have a look at the screen cast and let us know if we have missed anything in the process. Any further inputs from your end may help us.
,
Mar 15 2018
I attached a video. If I open the local test.html directly in Chrome, key events are prevented correctly. (like your screen cast) But if I serve the test.html on local server (I use httpster for this), the key events are no longer prevented. As you can see from the video, the two tab contains SAME html code, but result is different.
,
Mar 15 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
,
Mar 15 2018
Sorry, new update: Even I serve the html in my local server, the key events can be prevented correctly if I open it in incognito mode. After trying each extensions I install, I found it is caused by Tampermonkey So please close this, this is not a Chrome bug. Sorry for this report.
,
Mar 15 2018
Thanks reporter for confirming the extension issue. Closing as per request. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by viswa.karala@chromium.org
, Mar 14 2018