Description of the issue:
Other browsers (notably Chrome and Safari) will remain in the background when links in other apps (like Mail) are COMMAND-clicked. Brave, however, insists on coming to the foreground.
How can this issue be reproduced?
Set Brave as default browser.
COMMAND-click a link from a Mail.app message.
Observe Brave comes to the foreground and loads the link.
Expected result:
In keeping with the behavior of other apps, Brave should remain in the background while loading the COMMAND-clicked link.
Hi @meadowsr,
You should be able to set Mail to open as default. Open Mail > Select Preferences from the Mail menu > click General. There you should be able to choose your email app from the ”Default email reader” pop-up menu.
I need more detail on the issue and the expected results.
What kind of links are you clicking? If it’s a url, it’s going to open a browser.
What other apps besides mail?
What do you expect cmd + click to do?
I’m not sure what else I can add beyond my initial post, but I’ll try.
Let’s say Safari is set to be the default browser.
In Mail.app, simply clicking a URL in a mail message opens that URL in Safari, and Safari comes to the foreground.
COMMAND-CLICKING that same URL in that same mail message opens that URL in Safari, BUT SAFARI REMAINS IN THE BACKGROUND AND THE MAIL APP REMAINS IN THE FOREGROUND. Using the command key (⌘) modifier keeps the foreground app in the foreground and the destination app in the background (while it still loads the clicked URL).
The exact same behavior happens when Chrome is set to be the default browser.
The exact same behavior happens when Firefox is set to be the default browser.
The exact same behavior occurs when I click a link from other (but admittedly, not all) apps, like MailMate or Slack.
However, when Brave is set to be the default browser, COMMAND-CLICKING a link in those other apps behaves the same as a simple click: the URL is opened in Brave and Brave insists on coming to the foreground. Since Brave is a relative of Chrome, I’d expect similar behavior to Chrome, which is to remain in the background.
@meadowsr, that is a perfect explanation. I’ve tested it and I am also experiencing the behaviour with Brave. After doing some looking into, there is an issue open for this. I don’t have and cannot give you a date for the fix, but there’s a ticket open for it.