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

Opening PWA opens Brave #16388

Open
MarioMatschgi opened this issue Jun 12, 2021 · 8 comments
Open

Opening PWA opens Brave #16388

MarioMatschgi opened this issue Jun 12, 2021 · 8 comments
Labels
Chromium/waiting upstream Issue is in Chromium; we'll likely wait for the fix feature/pwa OS/Desktop priority/P5 Not scheduled. Don't anticipate work on this any time soon. repros-on-chrome

Comments

@MarioMatschgi
Copy link

MarioMatschgi commented Jun 12, 2021

Description

Installing a PWA, quitting Brave and then launching the PWA causes Brave to open as well with a new window

Steps to Reproduce

  1. Go to a PWA (My own PWA, Spotify)
  2. Install the PWA (click "install")
  3. Close the PWA and Brave
  4. Open the PWA

Actual result:

The PWA opens AND Brave opens as well

Expected result:

The PWA opens BUT NOT Brave

Reproduces how often:

Easily reproduced, just open any installed PWA while Brave is quit

Brave version (brave://version info)

Brave 1.25.72 Chromium: 91.0.4472.101 (Official Build) (x86_64)
Revision af52a90bf87030dd1523486a1cd3ae25c5d76c9b-refs/branch-heads/4472@{#1462}
OS macOS Version 11.4 (Build 20F71)
JavaScript V8 9.1.269.36
User agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.101 Safari/537.36
Command Line /Applications/Brave Browser.app/Contents/MacOS/Brave Browser --enable-dom-distiller --disable-domain-reliability --no-pings --origin-trial-public-key=bYUKPJoPnCxeNvu72j4EmPuK7tr1PAC7SHh8ld9Mw3E=,fMS4mpO6buLQ/QMd+zJmxzty/VQ6B1EUZqoCU04zoRU= --sync-url=https://sync-v2.brave.com/v2 --lso-url=https://no-thanks.invalid --variations-server-url=https://variations.brave.com/seed --enable-features=WebUIDarkMode,AutoupgradeMixedContent,SafetyTip,LegacyTLSEnforced,ReducedReferrerGranularity,PasswordImport,PrefetchPrivacyChanges --disable-features=NotificationTriggers,HandwritingRecognitionWebPlatformApi,FledgeInterestGroups,IdleDetection,FlocIdComputedEventLogging,HandwritingRecognitionWebPlatformApiFinch,InterestCohortFeaturePolicy,LiveCaption,AutofillServerCommunication,SubresourceWebBundles,NetworkTimeServiceQuerying,LangClientHintHeader,WebOTP,SignedExchangePrefetchCacheForNavigations,SharingQRCodeGenerator,TrustTokens,DirectSockets,InterestCohortAPIOriginTrial,FledgeInterestGroupAPI,AutofillEnableAccountWalletStorage,FirstPartySets,FederatedLearningOfCohorts,EnableProfilePickerOnStartup,TextFragmentAnchor,SignedExchangeSubresourcePrefetch,TabHoverCards --flag-switches-begin --flag-switches-end
Executable Path /Applications/Brave Browser.app/Contents/MacOS/Brave Browser
Profile Path /Users/Mario/Library/Application Support/BraveSoftware/Brave-Browser/Default
Variations aed3cac0-3f4a17df7146a73c-3f4a17dfc63a3c82-3f4a17df

Version/Channel Information:

  • Can you reproduce this issue with the current release?

  • Yes

  • Can you reproduce this issue with the beta channel?

  • Yes

  • Can you reproduce this issue with the nightly channel?

  • Yes

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields?

  • No

  • Does the issue resolve itself when disabling Brave Rewards?

  • No

  • Is the issue reproducible on the latest version of Chrome?

  • Yes (Chrome 91.0.4472.101)

Miscellaneous Information:

If this is a Feature and not a Bug: A setting for reverting back to the original behaviour (That opening the PWA does not open Brave) would be nice

@rebron rebron added feature/pwa needs-investigation A bug not 100% confirmed/fixed labels Jun 21, 2021
@rebron rebron added repros-on-chrome Chromium/waiting upstream Issue is in Chromium; we'll likely wait for the fix priority/P5 Not scheduled. Don't anticipate work on this any time soon. and removed needs-investigation A bug not 100% confirmed/fixed labels Nov 12, 2021
@jeannnemelanie
Copy link

Same issue here, with 2 differents PWA 😢
Any news for this ticket ?

@MarioMatschgi
Copy link
Author

Same issue here, with 2 differents PWA 😢
Any news for this ticket ?

Sadly not - still same issue, even on the newest version of chrome
Also quitting the browser while a PWA is opened will also close the the app, even though they are separate "apps" (in macOS Task-switcher, TaskManager, doc, etc.

Seems to be an issue of chromium itself

@jeannnemelanie
Copy link

Yes I can confirm, same thing is happening with Google Chrome PWA. And quitting the browser while a PWA is opened will also close the the app in both Chrome & Brave. Hope Chromium will work on it.

@ChaliceChore
Copy link

Still no solution for this?

@webknows
Copy link

Here's to hoping...

@rabinadk1
Copy link

I also can reproduce the issue.

@JStrategic
Copy link

Interesting that this still hasn't been addressed. Seems to be a long standing issue.

@AntoG87
Copy link

AntoG87 commented Mar 3, 2024

Same happens to me. Is there any update on this? Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Chromium/waiting upstream Issue is in Chromium; we'll likely wait for the fix feature/pwa OS/Desktop priority/P5 Not scheduled. Don't anticipate work on this any time soon. repros-on-chrome
Projects
None yet
Development

No branches or pull requests

8 participants