-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Persistent stuck notifications and badge count #3059
Comments
I've seen behaviour like this when the server is struggling so this is likely to be the HS trying to decide what our notification count should be. |
Do we get any more information other than the notif count for each room? It'd be nice if Riot-Web could say "I've already binged for event ID ABC123, I'm not going to do it again". |
this sounds almost the same as #3060? |
Different - This one the notification did go away for a bit, but then returned. #3060 seems to never go away until you go to a random room. |
I managed to encounter something similar to this (and by proxy, #3060 as well) with some help from element-hq/element-meta#486 (so this might actually be invalid/a different issue):
Edit: Muting the room doesn't help :/ |
related to #2427 |
I have a stuck notification too, it’s been like that for ages. Driving me nuts. |
@jurf if you sequentially browse every room where you're a member, without bothering to page up or down to tell whether there's the thing that caused the notification, then does the notification disappear? |
@grahamperrin I did that once before and it only maybe 1 out of 2 disappear. This time the other one disappeared too. Thanks! (Btw the culprit was the Riot room.) |
@jurf thanks for the feedback. (A couple of days ago I submitted, from within Riot, a bug report that might partially explain your most recent incident. Too soon to tell whether that report equates to an existing issue.) |
Not fixed for me |
I got this too in all my clients so it must be something core that makes this one notification count apear |
Is this issue still a defect you're experiencing? We think it needs to be closed - it will stay open for now but will be closed next week if we haven't heard anything. Thanks! |
The slow server case has not been fixed, nor has the switching between notification levels (to my knowledge) |
What happened:
What I expect to happen:
The (1) should disappear and not come back as I was not binged in that room anymore.
What actually happened:
It kept reappearing. I had to mute the room.
The text was updated successfully, but these errors were encountered: