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

Unread email badge next to email folders are only refreshed on app restart #659

Open
casasfernando opened this issue Aug 22, 2021 · 2 comments

Comments

@casasfernando
Copy link

casasfernando commented Aug 22, 2021

What Happened

Unread email badges next to email folders are only updated on app start.
If I read the unread emails in a folder the badge of unread emails is not updated.
If I close and start the app again, then the badge of unread emails is updated with the right number of unread emails.

Expected Behavior

Unread email badge next to email folders should be updated as soon as the emails in that folder are being read.

Steps to Reproduce

  1. Go to a folder in your email account with unread emails.
  2. Read or mark read the unread emails. This should update the unread email badge right away.

Logs

N/A

Platform Information

elementary OS 6 Odin
Mail version: io.elementary.mail/focal,now 6.1.0+r613+pkg23~ubuntu6.1

@casasfernando
Copy link
Author

Would it be possible to check and add the unread email badge for every email folder in the email account and not just the 'system folders' (Inbox, Junk, etc.)?

At the moment Mail seems to only be adding the unread email badge to the 'system folders' so if there are unread emails in other folders in the email account the only way the user will notice it is to manually select the folder and also manually refresh the content with the new button in the conversation pane.

I was hesitant to open a new bug/feature request about it, but let me know if you prefer for me to do that.

Thanks.

@marbetschar
Copy link
Member

marbetschar commented Oct 7, 2021

@casasfernando for now I'm fine with having badge-related stuff in one place, because they don't behave as expected at all anyways - and having all aspects in one place makes it easier to get an overview of what needs to be done. Once they are "supposed to work" we can always make more granular issues.

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

2 participants