New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 755029 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Need to press CTRL+T four times for new tab, If the Keyboard Response Repeat settings is Changed

Reported by ilkertez...@gmail.com, Aug 13 2017

Issue description

OS: Windows 10 (x64) 
Chrome/Chromium version: 60.0.3112.90 ~ 55.0.2854

I have CTRL+T keystroke repeat issue in Chromium since many months. A new tab able to opens but I only pressed fourth time to CTRL+T. Likewise, CTRL+F (for find). Sometimes CTRL+W.

I'd changed the Keyboard response settings in the Windows Registry. Because of my keyboard response rate is very low. (You can research the keywords on Google for more detail info: increase repeat rate typing). 

I used the "FilterKeys Setter" called a tiny tool. It changed the FilterKeys Flag value to 3 from 126 (The Source code is also available):
https://geekhack.org/index.php?topic=41881.0

***

What steps will reproduce the problem?

1) Increase to Keyboard response setting (a BATch file): https://paste.ee/r/IRUoU
2) Log-off and Log-on.
3) After run to Chromium, mouse pointer to click 4-5 times to the blank/white area on Most-visited pages). (Purpose: To not cursor focus override to omnibar.)
4) Press to CTRL+T.

Result: Chromium/Chrome will only be able to open a new tab, but only fourth pressed to CTRL+T.

If you've patience, you're use Chromium for a few hours or a day. During this time/day, in this way using will be tiresome. I've been living this persecution every but every day!

***

For now, there is two solution: 

a) Back to default the keyboard response settings: 

1) Default Keyboard response setting (a BATch file): https://paste.ee/r/bxznl
2-4) Repeat the above steps.

b) Disable FilterKeys: 

REGEDIT4
[HKEY_CURRENT_USER\Control Panel\Accessibility\Keyboard Response]
"Flags"="122"

Result: Directly pressed to CTRL+T. Chromium now opens a new tab at once.

***

This issue haven't happened in older versions (until to M53 or until to Build 416994. Meanwhile, Opera and Vivaldi's last builds haven't the issue).

I spent many hours and found out which revision/commit started the issue. I would like to ask you to revert the commit:

Review-Url: https://codereview.chromium.org/2128243003
Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=626154
Cr-Commit-Position: 42d287c9658c6bfa1202275597f28399409e8603-refs/heads/master@{#416995}

 
Labels: Needs-Triage-M60

Comment 2 by derat@chromium.org, Aug 14 2017

Cc: derat@chromium.org pkasting@chromium.org sky@chromium.org
Components: UI>Input>KeyboardShortcuts
Labels: -Pri-3 Pri-2
Someone familiar with Windows keyboard input and accelerators ought to take a look at this. I don't know who that is, unfortunately.

The change that you identified just made these accelerators not get triggered by autorepeated events. It sounds like your custom repeat rate setting may be resulting in initial events incorrectly being reported as repeated. (But I don't know anything about Windows and am just speculating.)
This sounds potentially legit but I have no time to look at it and don't really know much about event handling.
Labels: TE-NeedsTraige-help
Seems it is out of scope from TE end as it is related to event handlers, adding TE-NeedsTraige-help label to move this out of our triaging bucket.

Could someone from dev team please take a look into this issue.
Thanks..!

Comment 5 by derat@chromium.org, Nov 3 2017

Cc: sadrul@chromium.org kpschoedel@chromium.org ananta@chromium.org
Just guessing at adding some people who may know more.
Status: Archived (was: Unconfirmed)
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Sign in to add a comment