Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve "Open in Brave" Extension Opening Brave Browser Twice in Chrome #88

Open
hubertjakubiak opened this issue Dec 15, 2023 · 3 comments

Comments

@hubertjakubiak
Copy link

The "Open in Brave" extension currently demonstrates a behavior wherein it triggers the Brave browser to open twice if installed within the Chrome browser. The anticipated functionality is for the extension to initiate the opening of Brave only once. Ideally, it should intelligently detect whether Brave is already active, and if so, open a new tab within the existing Brave window rather than launching a redundant instance.

To Reproduce the Issue:

  1. Install the "Open in Brave" extension within the Chrome browser.
  2. Close the Brave browser if it's currently running.
  3. Activate the extension either from an external application or a webpage.

Expected Outcome:

  • Brave should open singularly upon activation.
  • If Brave is already running (minimized or closed), triggering the extension should create a new tab within the existing Brave window.

Actual Behavior:

  • The extension currently prompts Brave to open twice, resulting in unnecessary redundancy.
@tinoucas
Copy link

I can reproduce this with "Open in Edge" from Yandex browser on Linux: two tabs are opened each time in Edge with the same url. Happens both from context menu and from domains set in settings.

Works fine otherwise.

@Brent-Sanchez
Copy link

I've never figured this problem out, but it's a conflict the chromium engine itself (i think). I have accidentally ended up with rotating brave clients launching (nightly, and brave senior) and thats pretty troubling lol. Could it be due to the interaction with this extension? Yeah, it could for sure. But another avenue here is the way winDOHz™ re-constructs your filesystem around you in real time lmao. I've been trying to make as many (non-private) paths to resources look as absolute as I can get them, and that seems to be helping quite a bit. UAC controls have twisted me up in a hurry and I think that's to blame.

I do not run chrome official for this reason though, the system will confuse extension calls, and it locks the machine up pretty quickly if you're not expecting a sync to occur with cosmetic extensions.

https://superuser.com/questions/1362386/always-show-absolute-path-in-file-explorer-address-bar

@tinoucas
Copy link

tinoucas commented Nov 4, 2024

As I said (and verified just now) I also happens in Linux when using "Open in Edge" from chrome. I admit I don't understand all your arguments here, but it's hard to justify this as a Windows-only bug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants