7

Chrome. Hit F12 and start typing. Those keystrokes used to go into the console, right? I'm not imagining things...

And then some giant free-standing penis decided that instead, the initial focus should be in the search box.

So you type, nothing appears in the console, you focus the console, and carry on.

Then you're wondering why your api calls aren't in the network tab. Caching issues? Event handler crapping out? No, it's because that command you tried to enter ten minutes ago is still in the search box and being used as a filter.

Because someone decided to change the default focus.

As a wise man once said: "who the fuck was that? Who's the slimy little communist shit twinkle-toed cocksucker who just signed his own death warrant?"

Why didn't anyone stop him? In the meeting where he suggested that, why didn't his colleagues grab him by the testicles and drag him out of the building?

Why?

Fuckers.

Comments
  • 4
    Very good questions. We need answers!
  • 1
    Use the better browser ;P
  • 1
    @BordedDev Firefox doesn't focus the command line either.

    But! That's because the console is available in all tabs if you hit ESC. Since that's one keystroke away, I think the new UX is good. The problem is that our muscle memory is now void. The devtools should get a keybind config.

    Relatedly, why the heck doesn't C-F focus the search box in the Chrome devtools? This is one of those few conventions that every tool on every platform agrees on.
  • 2
    @lorentz It does actually XD
  • 1
    @BordedDev not for me :/ Is there a setting for this? Are there meaningful UX settings for the dev tools?
  • 0
    @lorentz if you're using F12 (and the last tab you were on in is the console) it works, but I have my terminal in the "big"/multi line mode. Ctrl+shift+K to open it directly

    There is a settings page but most of the settings you have in chrome are on the relevant page instead of a central one, e.g. throttling is on the network tab, or are you looking for something different?
Add Comment