Issue metadata
Sign in to add a comment
|
Hotkeys doesn't work with non-US keyboard layout
Reported by
s.chebo...@gmail.com,
Dec 6
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36 Steps to reproduce the problem: 1. Switch to non-US keyboard layout (Russian for me) 2. Try to use some hotkeys such as Ctrl+T, Ctrl+W, etc What is the expected behavior? Expected hotkeys actions What went wrong? Hotkeys doesn't work until you switch back to US layout Did this work before? Yes 70 Chrome version: 71.0.3578.80 Channel: stable OS Version: Flash Version: My OS is Ubuntu 18.04, fully updated. Guest account is affected too so this is not any extension problem. As a part of this issue, Enter key does not work in russian layout on Whatsapp web interface site.
,
Dec 12
Unable to reproduce the issue on chrome reported version# 71.0.3578.80 using Ubuntu 17.10 with steps mentioned below: 1) Launched chrome reported version and keyboard layout is in English 2) Used the hot keys(Ctrl+T, Ctrl+W, Ctrl+H), observed all keys are working as excepted 3) Changed the keyboard layout to Russian, used the hot keys(Ctrl+T, Ctrl+W, Ctrl+H), observed all keys are working as excepted Note: In screencast at 20th sec keyboard layout is in English(en) and at 37th sec keyboard layout is changed to Russian(ru). Also tested the issue on Ubuntu 14.04, but unable to reproduce the issue. @Reporter: Please find the attached screencast and screenshot for your reference and let us know if we missed anything in reproducing the issue, let us know if this issue is specific to Ubuntu 18.04.
,
Dec 12
I also have the same issue with latest chrome (71.0.3578.98)
Steps to reproduce:
1 - open new tab, put the cursor in address bar or into search input ("Search Google or type URL")
2 - while keyboard layout is in english, hotkeys (ctrl+T, ctrl+W, f12) are working. If you switch to russian layout, they won't work anymore.
If none of inputs on page are focused, then everything is working fine.
Checked this on fresh vm with fully updated ubuntu 18.10 and 17.10.
In ubuntu 14.04 everything works fine.
,
Dec 18
Maybe be related to (or dup of) bug 911012? Adding Needs-Bisect because the original reporter claimed it worked fine in M-70. Testing team, please try the repro steps from comment #3.
,
Dec 19
As per comment# 4, adding Needs-Bisect label.
,
Dec 19
Able to reproduce the issue on reported version# 71.0.3578.80, #71.0.3578.98 and latest chrome 73.0.3644.0 using Ubuntu 17.10, hence providing Bisect Info Note: Issue is not seen on Mac and Windows Bisect Info: ================ Good build: 71.0.3567.0 Bad build: 71.0.3568.0 You are probably looking for a change made after 595453 (known good), but no later than 595454 (first known bad). https://chromium.googlesource.com/chromium/src/+log/30e11c9e9b9f5ab322a5c5fdb107e62b44d6215b..2c72cd9089bc3278bf3d2852c971325a9c07f097 Change-Id: I6595f6aa163a18c9724c50546ac8c84bc5c84a03 Reviewed-on: https://chromium-review.googlesource.com/1252685 @erikchen: Please confirm the issue and help in re-assigning if it is not related to your change. Adding ReleaseBlock-Stable for M-71, feel free to remove it if not applicable. Thanks!
,
Dec 19
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by gov...@chromium.org
, Dec 7