How do I disable Cmd-# keyboard shortcuts?

[wpar...@gmail.com]

I constantly rely on Cmd-# keyboard shortcuts to switch between specific browser tabs in Chrome while developing. With the recent addition of these same shortcuts to switch to specific tabs within Developer Tools, my workflow is now regularly interrupted by unexpected behavior:

I hit Cmd-3 (for instance), expecting to switch to the 3rd browser tab, but instead I get the Network panel in Dev Tools.

It's akin to being periodically smacked on the back of my head while trying to work.

How do I disable this undesirable behavior?

Thanks.

[sander...@holder.nl]

Any luck in finding a solution?

[Sam Dutton]

Do you mean you want to be able to disable Dev Tools shortcuts?

(Stating the obvious, Dev Tools shortcuts like Cmd-3 only work when the Dev Tools are open.)

Sam

[sander...@holder.nl]

Yes, and I know.

But I also use cmd-1 to 9 to switch between tabs. If for example in tab 3 Developer Tools is open and I switch from tab 1 -> tab 2 -> tab 3. Ik get stuck at tab-3 because from there it focuses on the developer tools (no on the tabs).

Another example:

 I use the developer tools to write some javascript in the console, if i need a reference from another website which is open on the fifth tab i can't navigate to it using cmd-5. I need to unfocus the developer tools and then I can cmd-5.

[wpar...@gmail.com]

I'm fine with most of the Dev Tools shortcuts, except those which override browser shortcuts. Especially (in my case) the Cmd-# shortcuts for switching directly to a certain browser tab.

And I get why you stated the obvious. It's important to make sure we're talking about the same thing here.

Thanks.

[rich.tin...@gmail.com]

Any solution to this?

Annoying the hell out of me

[daniel....@gmail.com]

Uh, this functionality is ludicrous. Let me explain :

  Tabbing browser windows is as crucial to the process of web development as your steering wheel is on your car.

  If you press play on your ipod, GRANTED you are focusing on music, but your steering wheel should still continue to drive the car.

It was a weak decision by Chrome developers. And at the very least be able to be toggled.

:D

On Friday, January 25, 2013 8:42:21 PM UTC-5, jaredwilli wrote:

From what I can tell this is working as it should. When the browser window has focus the shortcut keys do work to jump to different tabs when I do cmd/ctrl + 1-9. This functionality is consistent when working with the Devtools focused. 

Think of Devtools as a separate browser window. Have you tried undocking Devtools from the browser window, so it's in a separate window altogether?

When docked, it functions in the same way as if it were a separate window. It is itself a webapp after all. 

It seems to be working fine for me, as long as the focus is on what I am trying to do the shortcut key in, either the browser window or webpage I'm viewing or the devtools for a page.

Jared

[rahil...@gmail.com]

Agree, I also reply on CMD+(0-9) to switch between browser tabs and I don't want Chrome Dev Tools to ever interfere with that.

[Sam Dutton]

I've filed a bug: crbug.com/174606. 

Star it, if you think this functionality should be changed.

Sam

On 5 February 2013 21:12, <rahil...@gmail.com> wrote:

Agree, I also reply on CMD+(0-9) to switch between browser tabs and I don't want Chrome Dev Tools to ever interfere with that.

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[owen...@gmail.com]

I added a comment to the bug, but also wanted to post it here to try to gain more attention and hopefully revert this update:

I've tried my best to get used to this and not to simply complain about workflow changes. However, this change is fundamentally flawed. One of the google groups comments sums it up very well:

"Tabbing browser windows is as crucial to the process of web development as your steering wheel is on your car.

If you press play on your ipod, GRANTED you are focusing on music, but your steering wheel should still continue to drive the car."

Broken Use Case : 1) Debug a page issue 2) Command-2 to switch to a reference [BROKEN]

Broken Use Case: 1) Command-# between windows 2) End up on a page with dev window open and focused 3) Command-# now "trapped" by Dev window which breaks the tab switching [BROKEN]

Broken Use Case: 1) Using keyboard shortcuts to switch between IDE/Editor and Chrome 2) Try to switch to another window using command-# and can't. 3) No keyboard shortcut to switch focus from dev tools to main window. 4) I am now forced to use my mouse, to focus on the main window, which greatly slows me down [BROKEN]

I've been trying to get used to this change for a couple weeks now. It is noticeably slowing down my development, and I'm sure others.

At the end of the day the Dev Window is not a first class citizen, but a servant to that particular browser window. Do not treat it as a full blown window for the sake of consistency, as you are breaking fundamental workflows in the process

[p. stephen w]

#Me too!

Any updates on this?

The keybindings are getting in my way. I'd prefer to re-map them but disabling them would work too.

[PhistucK]

If you press F1 (or go to the settings of the Developer Tools otherwise), at least on Windows, there is a label -

"Enable Ctrl + 1-9 shortcut to switch panels"

Perhaps on macOS it is "Enable Cmd + 1-9 shortcut to switch panels".

Untick its checkbox. Does that help?

☆PhistucK

--

You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/f3839a1e-444e-493e-8815-ffd7cd748053%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.