Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on Notification dropdown doesn't consistently change items from "unread" to "read"

Post

Notification dropdown doesn't consistently change items from "unread" to "read"

+8
−0

It appears to me that the notification system is not consistently marking as "read" something I've clicked on. Sometimes it does, sometimes it doesn't. I've been trying to run some tests to see if there's a pattern, but I've not had enough of different types of notifications to see a pattern (and don't think I will).

For example, it doesn't appear to matter if it's a notification for an answer or comment. It doesn't appear to matter if it's on the same page I'm currently viewing or not.

However, when it fails, it fails spectacularly. I can click on the notification link over and over from different starting points and it will continue to claim to be "unread."

I'll continue to watch what's happening to see if I can detect a repeatable pattern. And the next time it happens at all, rather than clearing it out in frustration, I'll leave it in place and drop a note against this post to let someone know there's one in my queue they can look at.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

2 comment threads

Same tab? (8 comments)
It also happens to me sometimes, and I also couldn't figure out a clear pattern... (3 comments)
It also happens to me sometimes, and I also couldn't figure out a clear pattern...
hkotsubo‭ wrote about 3 years ago

It also happens to me sometimes, and I also couldn't figure out a clear pattern...

FoggyFinder‭ wrote about 3 years ago

Same here. It happens so rarely so I didn't bother to create Q by myself.

elgonzo‭ wrote about 3 years ago

Ditto, noticed this as well without having any suspicion about why it happens when it happens. Since i am not inundated with notifications, i never was bothered enough to keep an eye on it...