4

This stopped working recently, what happened? Is there a way I can configure it so that it would work?

Edit: So I verified with the following, apparently CTRL + , still works as traverse up, but not CTRL + .

This is across multiple installations I use so it is in the latest chrome on all my Mac OS machines.

(function a() {
    return function b() {
        debugger;
    }
})()()

Edit

It appears Chrome recently (Apr 2019) fixed this issue.

user2167582
  • 5,103
  • 10
  • 50
  • 95
  • Those are definitely listed [here](https://developers.google.com/web/tools/chrome-devtools/shortcuts) so they should still work. Did you do a Chrome update between when they worked and when they stopped working? Do other shortcuts listed on that page still work? – pushkin Mar 26 '19 at 21:41
  • A temporary workaround might be to build Chromium yourself, and modify the key bindings of the developer tools (see [here](https://bugs.chromium.org/p/chromium/issues/detail?id=174309#c56)). – char Mar 27 '19 at 08:04

1 Answers1

1

One thing that you can check is that if Ctrl+. and Ctrl+, is not mapped in operating system command shortcuts because it will take precedence over chrome shortcuts/shortkeys

paradox
  • 581
  • 5
  • 13