Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I've recently noticed Chrome (71) on Mac is now hijacking the `Command + Q` shortcut and asking if I really want to quit. I appreciate people will occasionally shut down a Chrome session by mistake, but it seems a little ironic that they're clamping down on behaviour hijacking in one space whilst implementing it in another.

(Caveat: I'm not sure if this change is being committed by a Google Chrome dev or non-Google Chromium dev)



AFAIK, this has been the case for quite some time now. There is a menu option to disable this -

Chrome > Warn before quitting (cmd+q)

I've disabled cmd+q on my system, so I haven't run into this recently.


When using Command + W to close a tab, it's only a fat finger away to close the entire browser. Years ago that happened and it was a huge hassle since it wasn't easy to reopen all the tabs you had.


wasn't "reopen recent tabs" a launch-day feature for chrome?


I'm not sure. I remember hitting Command+Q a few times by mistake and losing whatever tabs I had open. Maybe I didn't know about that feature at that time.


I came here to say this. It should really be an opt-in behavior rather than opt-out.

It's not the only reason chrome has become a not-so-good citizen on macOS: the memory/CPU footprint is bad enough, but it also does things like give system-like popups when a new printer is detected on my network. I'm not sure when I permitted chrome to do this, and it seems like it's trying to subsume more and more of my system's function without asking. I find the command + q thing to be a particularly annoying version of this.


I miss being able to use backspace to go back.


I saw that too. There's a menu option to disable it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: