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.

Post History

75%
+4 −0
Q&A When clicking "mark read" it shows a 0 when it should actually dissapear.

With a bit of effort, you can even do this: I think the code that shows the notification count draws the notification "container" (the blue circle) once, and then just updates the number from so...

posted 4y ago by Monica Cellio‭

Answer
#1: Initial revision by user avatar Monica Cellio‭ · 2021-01-08T01:35:33Z (almost 4 years ago)
With a bit of effort, you can even do this:

![-1](https://meta.codidact.com/uploads/9S2KQQorx8tf8JrjEManFFUg)


I think the code that shows the notification count draws the notification "container" (the blue circle) once, and then just updates the number from some data value.  Only when you close and reopen the notifications, or refresh, or move to another page, does the whole thing get rebuilt again.  I am not wise in the ways of front-end code, but I can see the logic here.  We *could* write some extra code to remove the blue circle entirely instead of showing "0", but "0" isn't wrong either.  (-1 is wrong but my own fault for provoking it.)

The first time I saw the "0" I actually smiled; I wasn't expecting it but it seemed like a reasonable thing to have happen.  Can I persuade you that what you see as a bug is instead a charming quirk, maybe even an Easter egg?