Notifications bell indicator stays lit after reading the last unread notification

[palmoni5]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Other

Body

When I have exactly one unread notification and I open it by clicking through to the page it points to, the unread indicator on the notifications bell in the global header stays lit. The notification itself is correctly marked as read on the notifications page, but the header indicator does not refresh to reflect that until I reload the page.

The confusing part is that this stale indicator is indistinguishable from a genuinely new notification. After reading my only notification I still see the dot, so I assume another notification arrived in the meantime, go back to the inbox, and find nothing new. With a single unread item this happens every time, because the indicator should go from "on" to "off" and instead it just never turns off.

Steps to reproduce

1. Get into a state where you have exactly one unread notification (https://github.com/notifications shows one unread item).
2. From any page, confirm the bell icon in the header shows the unread indicator.
3. Click the notification and follow it to the issue / PR / discussion it links to.
4. Look at the bell icon in the header on that destination page.

What I expected to happen

Once the last unread notification has been read, the header indicator clears without a full page reload, the same way the notification's own read state updates.

What happened instead

The header still shows the unread indicator. It only clears after a manual page reload.

Environment

github.com web UI, desktop browser, logged in as a normal user.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐