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.
Notification dropdown doesn't consistently change items from "unread" to "read"
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.
2 answers
I am not 100% certain, but during the few occasions i got a notification in recent days, i believe i might found a condition that seems to determine whether the unread/read state and the unread counter updates or not.
If i keep the notification drop-down open for about 5..10 seconds before clicking/tapping an unread notification, the unread counter gets updated.
However, if i click on an unread notification immediately (in less than 5..10 seconds) after opening the notification drop-down, the unread counter is not updated.
But i am still not sure whether this in fact is true, or whether my few observations (which i can't thorougly verify due to lack of received notifications) turn out to be a red herring. Hence, i would like to asks other users to keep an eye on how long they keep the notification drop-down open before clicking/tapping an unread notification, and confirm whether they can confirm my observations.
0 comment threads
This is (newly) happening for me today, using Firefox 93.0 on Windows 10. I haven't been using Codidact a lot on this machine lately, but I have used it in recent weeks without seeing this problem. A few days ago I updated Firefox to try to reproduce a different bug. I do not know if these facts are related.
I don't have a lot of extensions in this browser, but I disabled them one at a time and retested between, with no apparent change in behavior. (Tampermonkey, Stylus, AdBlock Plus, NoScript (all scripts Codidact uses are whitelisted), Tab Session Manager.)
I currently have one "unread" notification that I've read several times (same tab, and then navigating away as normal). I'll see what happens when I get back to the computer I normally use.
Update: In Chrome 95.0.4638.54 on MacOS 11.6 (Big Sur), I clicked on a notification (current community, not current page) and when that page loaded the notification was cleared.
0 comment threads
2 comment threads