Issue metadata
Sign in to add a comment
|
Cmd+Shift+] & Cmd+Shift+[ shortcuts for switching tabs no longer work
Reported by
russ...@russelldunphy.com,
Sep 15
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36 Steps to reproduce the problem: 1. Open multiple tabs in chrome 2. Press Cmd+Shift+] or Cmd+Shift+[ What is the expected behavior? Chrome moves between the different tabs, either to the right (Cmd+Shift+]) or to the left (Cmd+Shift+[). What went wrong? The tab stays the same Did this work before? Yes Immediately before updating to the new UI (so guessing 68.0.3440?) Chrome version: 69.0.3497.92 Channel: stable OS Version: OS X 10.13.6 Flash Version: I can't find any other reports that this shortcut has stopped working, however I have found this issue which looks to be somewhat related: https://bugs.chromium.org/p/chromium/issues/detail?id=699450&q=next%20tab%20shortcut&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified Could it be that these are actually MacOS system shortcuts that Chrome used to respect but now doesn't, for some reason?
,
Sep 16
Does it work for you in Canary? Which keyboard layout are you using? Do you use an non-english keyboard? Thanks in advance.
,
Sep 16
Ah - I'm so sorry! Really should have thought to mention that I use a Dvorak keyboard layout as it's obviously relevant here. I just tried with a standard British layout and the shortcuts still work in stable Chrome. I also tried with Canary and it works even with the Dvorak layout! This is such a relief. I thought Chrome might've just decided to stop supporting these particular shortcuts and I was going to have to relearn new muscle memory. Thank you!
,
Sep 16
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
,
Sep 16
Thanks for your feedback. Looks like this was fixed in issue 811921 and will work again in Chrome 70. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by meh...@chromium.org
, Sep 16