Fix badge notification bug when private mode is enabled #1260
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # source/browser/conversation-list.ts
CvX
approved these changes
Feb 5, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Take a look at #1257 for more context.
The basic issue was that the conversations event was being sent only in cases when private mode was not enabled. This was fine for the majority of cases, but led to a bug in the notification badges not showing up.
This is a proposed fix where I refactored the logic to just always fire the conversations event and just have the Touch Bar component handle the display logic - looking back, this makes much more sense, and I'm embarrassed that I didn't implement this the first time 😅
Thanks @danielfbnunes for pointing this out!
Fixes #1257