우선순위/심각도: 낮음
플랫폼: Windows/Android
설명: Windows와 Android에서 읽지 않은 개인 메시지 알림이 표시되지만, 이를 클릭하면 페이지가 존재하지 않거나 비공개라고 표시됩니다.
메시지를 읽을 수 없으므로 알림을 해제하는 방법이 없는 것 같습니다.
재현 단계: 재현을 시도해 보지는 않았지만, 발생한 상황은 메시지가 읽지 않은 상태로 남아있을 때 수신자에서 제외되어 더 이상 메시지를 볼 권한이 없게 된 것입니다.
2개의 좋아요
Does the number disappear when you reload the site?
That’s what I did to get rid of the notification for a like when someone has liked one of my posts and deleted it immediately afterwards.
1개의 좋아요
Nope, still there
1개의 좋아요
I was able to reproduce the issue.
Clicking Dismiss removed the notification
1개의 좋아요
If you can not dismiss it from the top, maybe try dismissing it from your profile, notification tab (there is a dismiss all) ?
I guess there are 2 questions here
-
How did the bug happen (my guess, maybe being kicked out of a PM can trigger this)?
-
How to get this annoying notification to go away (hopefully the dismiss stuff helps)
2개의 좋아요
I followed the steps from the first post
- Send a message to a user
- Remove the user from the message
- Log in as this user
- Get rid of the notification by dismissing all notifications
2개의 좋아요
This still happens, and it is still difficult to get rid of the notification. In particular, you cannot dismiss the single notification, so you first have to check all the other notifications caused by messages.
To some extent, this is even a security vulnerability, as the user should no longer have access to the title of the message.
2개의 좋아요
I put a note for the team to triage in the next few weeks.
2개의 좋아요
Is there any news on this?
I still find it concerning that users I remove from a PM can still see title changes. This affects my ability to rename a topic that I convert into a personal message. There is a reason why I remove the user, and I don’t want them to have access to the new title.
2개의 좋아요
I’ll see if i can reproduce 
2개의 좋아요
We were indeed missing some “cleanup” path when removing users from PMs (either directly or through a group).
2개의 좋아요
I think that’ll also fix Sticky unread reply notification.
This has been open for a while now. Is there anything else needed for this, or has there simply been no time to review and merge it so far?
I have been working on fixing the root cause of several related inconsistencies regarding notification counts so my above PR has been superseded by this one
1개의 좋아요
This got delayed quite a bit by lots of changes in the affected area around the same time this was being worked on. Those PRs got too stale to revive — and I also noticed that it was my own doing that delayed these because I was the one making all of the changes in that area. So, I took this one on and have just merged a fix.
I believe this is correct, and am also unsure it was still broken currently. Either way, it should definitely might be fixed after this merge.
2개의 좋아요