delay on delete (fn + backspace) for ~2 seconds
Reported by
d...@haage.info,
Oct 6 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/604.3.1 (KHTML, like Gecko) Version/11.0.1 Safari/604.3.1 Steps to reproduce the problem: 1. go into any field (even location bar) 2. put cursor in the middle/beginngin of the content 3. forward delete (fn + backspace) What is the expected behavior? no delay, similar to backspace, or any other keystroke What went wrong? each keystroke that involves the function key is delayed by ~2seconds. (tested with fn + backspace, fn + cmd + backspace) This happens in all input fields, location bar, almost always. Did this work before? N/A Chrome version: Version 61.0.3163.100 (Official Build) (64-bit) Channel: beta OS Version: OS X 10.13.1 Flash Version: first discovered in VC code, tracked down in current chrome on Mac. System freshly booted, mostly idle and only chrome running.
,
Oct 9 2017
dirk@ Thanks for the issue. Unable to reproduce this issue on Mac OS High Sierra 10.13 and Mac OS 10.12.6 using the latest Canary 63.0.3236.0 and Stable 61.0.3163.100 following the below steps. 1. Launched Chrome and navigated to random page. 2. Put the cursor on the url and hit fn+delete (backspace) key. Could observe that the characters are getting deleted without any delay. Please find the attached screen cast for reference and confirm if anything is missing from our end. Thanks..
,
Oct 9 2017
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
,
Oct 9 2017
Ok, I made an additional check: same macOS (and same computer), same chrome installation but I created a new user account. Neither Chrome nor Code show this problem there. Not sure how to proceed from here, because it happens in my main user account.
,
Oct 11 2017
dirk@ Request you to please reset your chrome settings by navigating to chrome://settings -> Reset, reset all the flags at chrome://flags -> relaunch Chrome and retry the issue. If there are still any issues, please update the thread for further triaging. Thanks..
,
Oct 11 2017
that did the trick (still not in Code though). Will reopen this bug when it reappears. Thank you.
,
Oct 11 2017
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
,
Oct 12 2017
As per comment #7, closing the issue as wontFix. Please feel free to raise a new issue if able to reproduce the issue using latest chrome builds. Thanks...!! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by manoranj...@chromium.org
, Oct 6 2017