-
Notifications
You must be signed in to change notification settings - Fork 974
Notification bar is still visible after restart #8435
Comments
Is this specific to the extension pane ie after changing the lang setting as well? |
didn't test with the language |
which X should I click? I hit "yes" to restart but couldn't reproduce. Notification was hidden as expected. Running SHA 506036e, macOS Sierra. |
@cezaraugusto X as in aplication X 😃 don't click anything on the notification |
ok I think that's because window closing on Mac isn't necessarily a restart. Unless you cmd+q to close, window will be refreshed but app is not restarted. That would work with Win/Linux where close icon really means closing the app, but not on mac. You could check that by disabling webtorrent and closing with the X, then try to download a torrent. On restart, notification is still active (bug per this issue) but that's because webtorrent is still active, since clicking on the download file would redirect to webtorrent page. So notification is still on because extension is still on -- until you restart. |
btw there's a conditional in our code indicating that behavior on mac here: https://github.com/brave/browser-laptop/blob/master/app/index.js#L235 you can see that app will quit on all OSes except darwin (mac) |
working as designed see above ^ |
I am not able to verify this on Win x64 preview 2 due to #8629. Tried building it from source and packaged build. |
@srirambv this is invalid. It's working as designed. |
Did you search for similar issues before submitting this one?
yes
Describe the issue you encountered:
Notification bar is still visible after restart
Platform (Win7, 8, 10? macOS? Linux distro?):
macOS
Brave Version (revision SHA):
570587f
Steps to reproduce:
Actual result:
Notification is still visible
Expected result:
Notification shouldn't be visible, because you just restarted your browser
Will the steps above reproduce in a fresh profile? If not what other info can be added?
yes
Is this an issue in the currently released version?
Can this issue be consistently reproduced?
yes
The text was updated successfully, but these errors were encountered: