Home Forums Mac Software Mac Operating Systems macOS 14.2

Minor fixes in SwiftUI and some Kits effecting developers. No major fixes noted.

I was wondering about the necessity for this feature, but "people facing extraordinary digital threats" clarifies it.

macOS 14.2 has been released, and while ⌘ ⇧ caret bug in Safari has been squashed, the ⌘ ⇧ N bug, also in Safari, and the less annoying of the two, remains.

I just updated to macOS 14.2.1, and the ⌘ ⇧ N bug in Safari remains intact!

Artie could you remind us what the ⌘⇧N bug in Safari is? I just tried it and, as expected, it opened a new private browsing window. I am running Safari Version 17.3 (19617.2.1.11.3).

Artie, I've been holding at Monterey for a while now and wanted to get your opinion on the Sonoma experience....and I KNOW you have an opinion!

The reason I ask goes to a simple challenge....my automated HomeKit household keeps asking me to upgrade to the latest HomeKit framework, and for IOS 17.2 this is not an issue, but for my desktop computing it would lose connection once the HomeKit upgrade was applied unless I ALSO upgrade my MacOS to Sonoma.

Thanks in advance for your thoughts on this....

Rats! I keep tying ⌘ ⇧ N when I mean ⌘ ⌥ N, which bug you confirmed previously. "New Window," NOT "New Private Window."

Sorry for the confusion.

To be perfectly honest, anything other than the present Safari bug has "seamlessly" inserted itself into my workflow and no longer bothers me. (I'm certain that there's other stuff, but there's nothing "in my face.")

So, I can't think of any substantive reason why you shouldn't upgrade, but, of course, make sure you've got an up to date Monterrey clone if oyu're not using Time Machine.

Sorry for my leaky memory. Anyway, I just tested ⌘ ⌥ N and while it did not open a full size window, it did open a mini window that other than size was a fully functioning new window, but probably because of the size, I almost missed its opening. This was using Safari Version 17.3 (19617.2.1.11.3) in macOS 14.3 Beta 1.

I have an extensive HomeKit network and for what it is worth, HomeKit has been oblivious to any OS upgrade or update. The only upgrade issue ever was some older HomeKit devices that refused to play-nice when I switched to a mesh router and had to either be replaced or their firmware updated.

The macOS 14.2.1 update did not include an update to Safari, which remains at version 17.2.1, so I guess your mini-window - whatever the logic behind it may be - is a function of your version 17.3.

Now I'm confused. In Safari isn't Command-N a new window? I don't see Command-Option-N as a key command in Safari's File menu.

It appears to mimic a feature in the Arc browser. ¯\_(ツ)_/¯

To paraphrase an old song "The shortcuts, they are a-changing". I'm not sure which version of Safari the change occurred, but in Safari 17.2.1 and 17.3 they are...

• ⌥⌘N - New Window
• ⇧⌘N - New Private Window
• ⌘T - New Tab
• ⌥⌘T - New Tab at End
• ∧⌘N - New Empty Tab Group

NOTE: The Cheatsheet app will display all the shortcuts for the foreground app with a single keystroke. For someone like me, it is very handy.

Strange feature. I wonder how you expand it to a full sized window?

Although it doesn't appear in my file menu, ⌘ N gets me a new tab, same as ⌘ T.

Which version of macOS & Safari are you in, Ira?

I am in Safari 17.2.1 and ⌘ N opens a new window, not a tab. And ⌘ N is listed in my File menu as New Window, contrary to the post above.

More than passing strange!

Take a look at this! (I wonder why IMGUR has stopped offering me a magnifier?)

⌘ N calls up a new window for me only if I've got Safari launched but with NO windows open.

¯\_(ツ)_/¯

I have the same Safari menu you have, and Imgur still offers me a magnifier. ¯\_(ツ)_/¯

Very weird because this is what mine shows.

Very weird indeed!

Not to mention that IMGUR gives me a magnifier when I click on your link, but not when I click on mine.

This ¯\_(ツ)_/¯ has become a go-to item lately!

BACK TO THE SHORTCUTS ISSUE. and conceivably this is all related. I had always assumed (there's that D@** word again) that a keyboard shortcut defined in the foreground application would take precedence over the same shortcut in running applications in background. But I just proved to my satisfaction that is not necessarily true. As long as the number of active applications is reasonable and/or those applications have a reasonably limited number of keyboard shortcuts duplicate shortcuts seldom cause any problems. But as I look at what is running on my system today the number of active applications continues to grow and the number of shortcuts defined by each application is growing rapidly. Given there are a very limited number of modifier keys it is inevitable developers will define duplicate keyboard shortcuts to trigger them. The problem becomes when I press a given keyboard shortcut does it the foreground or backgound app? The case I encountered was a commonly used keyboard shortcut in my browser was triggering a menu in a background app that was hidden behind the foreground app. Once I finally tumbled to what was happening it was a simple matter to add another modifier key to the background app's shortcut -- but I probably created another conflict with another app. Too D@** many keyboard shortcuts not too.

I'm certain that I've never got as many apps running at the same time as you, so I'm less susceptible to conflicts.

When I was first setting up my Butler shortcuts many years ago, I occasionally got undefined conflict pop-ups which I chose to ignore 'til they resolved in real life, and the only one that's ever come back to haunt me was having set ∧ C for some long forgotten purpose and having had it override the command as used to halt a process in Terminal. I'm not even sure if the app in question was running at the time.

The only other problem I've run into was trying to use the ⌥ key as a modifier with an app - maybe Firefox and/or Safari - and finding that rather than accommodating my intention, it caused an alternate version of the app to launch.