but thats one of the main reasons I keep using Safari, holding cmd+Q is annoying
if you accidentally close safari just open it and cmd+shift+T brings everything back
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
(RANT) Safari is a literal piece of (beep)
- Thread starter Shirasaki
- Start date
- Sort by reaction score
if you accidentally close safari just open it and cmd+shift+T brings everything back
Oh ok. If only that works across all scenarios: multiple windows (not just tabs), websites that opened through navigating around, and more. Besides, those browsers might have an option to turn off that safely feature (or maybe I’m wrong since I have no reason to turn that feature off) where safari is “the Apple way is absolutely the best way and all other ways are just wrong wrong wrong wrong wrong”.
This article explains the problem and a solution for Cmd-Q in Safari:
Quit Confirmation for Safari on MacOS
Now I can wildly stab at ⌘W to close tabs without a care in the world.daringfireball.net
...
Back in February, KALLT described a way of using an Applescript in an Automato Quick Action that could be put in the Safari Services menu. The result is that cmd-Q calls the script ONLY in Safari, prompting a dialog asking if you want to quit. I've been using this for over a month and it works great. So if you are one of the people asking for a way to modify cmd-Q in Safari, this is it. It's on page one of this thread. Kudos to frou and KALLT.
The Chrome command+Q is a little broken.
I have a website that asks the user for confirmation before they leave the page. Chrome's command+Q handling happens first, before the webpage itself asks for confirmation. If I agree to Chrome's command+Q confirmation (not realizing that I have unsaved changes on the web page), then the page closes. I then get the warning from the website to save my changes, but Chrome has already closed the page.
In point of fact, the webpage is kind of still open. It shows as an entry under the "Window" menu. But, the page is invisible.
I have a website that asks the user for confirmation before they leave the page. Chrome's command+Q handling happens first, before the webpage itself asks for confirmation. If I agree to Chrome's command+Q confirmation (not realizing that I have unsaved changes on the web page), then the page closes. I then get the warning from the website to save my changes, but Chrome has already closed the page.
In point of fact, the webpage is kind of still open. It shows as an entry under the "Window" menu. But, the page is invisible.
iPad OS 15.4.1. Reading List now changing the address for some items and directing me to a completely different webpage. Permanently broken, so if I don’t recall broadly where the original webpage was then it’s lost forever. Sigh.
ETA: Apologies for putting this in a Mac thread. I cross-posted with another Safari related topic I was reading, but hopefully this is broadly relevant as it encompasses all of Safari and iCloud.
ETA: Apologies for putting this in a Mac thread. I cross-posted with another Safari related topic I was reading, but hopefully this is broadly relevant as it encompasses all of Safari and iCloud.
Last edited:
But because iCloud bookmark syncing is FUBAR, the broken Reading List items remain intact on my Mac as they haven't yet propagated. Every iCloud bug has a silver lining!
What a calamity Apple has become.
I work around this by setting a custom keyboard shortcut in System Preferences to replace Safari's Quit keyboard shortcut with ⌥⌘Q.
System Preferences > Keyboard > Shortcuts > App Shortcuts, if you'd like to do the same:
But it doesn’t work on monterey for some reason after multiple tries. So I gave up fiddling around.
Works just fine for me, always has. In fact, just deleted that shortcut and reentered it, working perfectly.
You are using option+command+Q, right? It's the only single modifier key that's free to be used with command in Safari without triggering a system keyboard shortcut (shift+command+Q is log out, control+command+Q is screen lock).
I already forgot, cause I just installed third party program to provide quit prompt and moved on.
After using it for several months I've actually given up on the AppleScript, because the data it inspects seems be on some kind of time lag, or just plain wrong.
For example, it's quite common I'd get the quit confirmation dialog saying "Are you sure you want to quit, there are 3 windows and 5 tabs" at a time when I DEFINITELY had only 1 window and 1 tab remaining. So the quit confirmation dialog became pointless because I always had to question whether it was a false positive. I thought this might just be a Big Sur quirk, but now that I'm finally on Monterey, it still happened.
Last edited:
