Thanks for reporting it! one additional note is that this is a client/server mismatch… if I keep the same window open and open a test user in a different browser, the notification dot can appear, but it goes away on refresh despite not changing the read state. Impersonation effectively causes the same behavior as the refresh.
This will fix it
main ← ux-fix-chat-unthread-indicator
merged 03:29PM - 09 Sep 26 UTC
Replying to someone in a channel with threading disabled leaves no unread indica… tor, because the reply was tracked as a thread message while rendering in the channel stream. Essentially we have an expectation that the threading interface will handle this state, but don't have coverage when threading is disabled.
This fix counts those replies against the channel's read marker, so both the unread dot and mentions inside the reply now show up when threading is disabled.
Issue originally reported here: https://meta.discourse.org/t/chat-notifications-not-showing-for-replies-in-chat-channels/410620
To repro:
1. Create channel with threading disabled
2. Post a message in that channel, then navigate away from the channel
3. Open an incognito window and log in as a different user
4. Join the channel and reply to that first message
5. Switch to the original user, and note that you can see the unread dot in the sidebar
6. Refresh the page, you'll notice the unread dot in the sidebar goes away despite not having visited the channel
2 Likes