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.
Notifications sometimes stay unread after clicking
I noticed that sometimes when I click notifications, they keep reappearing after I refresh. If I refresh several times, and click several times, eventually it "sticks" and they become read. I don't think it makes a difference to open in current tab vs. new tab. I'm not sure about exact steps to reproduce, but it happens very often to the point where I don't "need" to reproduce it.
I use Firefox fork with many privacy addons, I won't list them all here. I think it would be more useful to figure out what specifically is required for this bug to not happen, so that people can adjust their set up accordingly.
- Does anyone else experience this?
- What causes it?
I assume that when I click on the notification, some kind of request is sent to the CD API to the tune of "mark notification 123 as read". You'd think that this would either work or not. What could possibly make it work sometimes?
Kind of a dupe of https://meta.codidact.com/posts/275896, but that question has less detail, no activity since 3 years, and the asker has not been active in 2 years.
1 answer
I suspect the add ons and fork mentioned are not relevant. I see a persistent notification circle on standard Firefox with no add ons. It doesn't seem to be completely consistent but the general behaviour I see is as follows:
- I see a blue circle indicating I have a notification.
- I open the notifications panel and click on the notification.
- The relevant page opens, showing the answer or comment the notification referred to.
- The blue circle is still present at the top of the page and the notification is still marked as unread.
- If I open the notifications panel while already on this destination page, clicking on the notification takes me to the answer or comment (which does not involve changing to a different page) and the blue circle disappears and the notification is marked as read.
Note that this behaviour when already on the destination page seems to depend on it being the exact destination (so the URL of the answer to a question if the notification referred to that answer - the URL of the question is not sufficient). This makes me wonder if it is the lack of requirement for a page load that allows the functionality to work, and a page load suppresses it, causing the mark as unread to fail.
2 comment threads