Community-edition: Tab unread counter doesn't work on all services

[kr3t3n]

Steps to reproduce

1. Enable services like GMail, MS Teams, Roundcube
2. Receive new message/email
3. Tab counter is not showing

Expected behavior

I expect the services to show unread messages/emails like the others do, like Hangouts, LinkedIn, WhatsApp, etc.

Actual behavior

Rambox unfortunately does not show tab counter for unread messages for the services listed above (GMail, MS Teams, Roundcube)

ENVIRONMENT

Windows 10

Rambox: v0.6.3

OS: Windows 10

Arch: x64

[welcome[bot]]

Thanks for opening your first issue here! Be sure to follow the issue template!

[dguyonvarch]

Gmail & Roundcube works for me :thinking:

But for MS Teams, i have opened a new issue #2020 with a PR #2021
Paste this in Teams custom code in the meantime :

function checkUnread() { 
   updateBadge(angular.element(document.documentElement).controller().pageTitleNotificationCount);
}
function updateBadge(e){
   e>=1 ? rambox.setUnreadCount(e) : rambox.clearUnreadCount()
}
setInterval(checkUnread,3000);

[kr3t3n]

Gmail & Roundcube works for me 🤔

But for MS Teams, i have opened a new issue #2020 with a PR #2021
Paste this in Teams custom code in the meantime :

function checkUnread() { 
   updateBadge(angular.element(document.documentElement).controller().pageTitleNotificationCount);
}
function updateBadge(e){
   e>=1 ? rambox.setUnreadCount(e) : rambox.clearUnreadCount()
}
setInterval(checkUnread,3000);

Any idea what I could do to force Gmail & Roundcube to work for me too?

[maxerbox]

Gmail Fixed in #2034

[kr3t3n]

GMail and Teams work now but Roundcube still doesn't. Any clue how to fix that?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically closed since there has not been any recent activity. Please open a new issue for related bugs.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.