I just discovered this odd issue in Safari 12 under macOS Mojave (10.14). It might exist in older versions of macOS but I didn’t start using full-screen—and Mission Control—in earnest until around macOS Mojave (10.14). And it’s reproducible from my experience across multiple macOS installs between my personal machines, the Apple store machines and even on my work computer.

Open up Safari, click the green dot in the upper left-hand corner to make this screen fullscreen and then hit the key combo for a new window in full-screen mode: Option+Command+N. Nothing happens.

Now move your mouse over to the “File” menu in Safari and just toggle it. With that done, hit the key combo for a new window in full-screen mode again: Option+Command+N. It works! Not only that, it works from that moment forward without any toggling of the “File” menu dance.

Is this a bug or a feature? If it’s a bug, how can I report it to Apple? If it’s a feature… Why is this desired functionality?


2 Answers 2


This is a known issue at Apple and after nearly 2 years — and two major macOS updates — it still has not been addressed.

For anyone still frustrated by this seemingly basic issue, it still exists in Safari 14.0.1 running on macOS Bug Sur 11.0.1 (20B29). That means this issue has survived two full major macOS releases and two major Safari updates.

Additionally, I reported this issue on Apple’s official feedback (bug tracking) system on Mar 20, 2019 and it was closed it on Mar 25, 2019 as follows:


Mar 25, 2019 at 11:21 AM

Engineering has determined that your bug report is a duplicate of another issue and will be closed.

The open or closed status of the original report your bug was duplicated to appears in a text box within the bug detail section of the bug reporter user interface. For security and privacy reasons, we don't provide access to the original bug yours was duped to.

If you have any questions or concerns, please update your report directly at this link: https://bugreport.apple.com/.

I find it fairly stunning that two years later this issue still exists.


This is definitely a bug. I've experienced the same thing. You can submit a report here.


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .