What happened:
I got binged in a room. Riot's favicon went to (1) and the room went to (1). I clicked the room. I read the message. The (1) disappeared on both. I swapped to another room. The (1) came back on both favicon and room. I swapped to the room. It disappeared. Rinse repeat at least 8 times (enough that I demonstrated this to @lukebarnard1 ).
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.
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 #3261 (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鈥檚 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.)
May be fixed by https://github.com/matrix-org/matrix-react-sdk/pull/3121~~
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
Most helpful comment
I have a stuck notification too, it鈥檚 been like that for _ages_. Driving me nuts.