Users reported that read topics in Discourse’s /latest and /categories views were not visually distinguishing themselves from unread ones — appearing black instead of greyed out — making it hard to track what they’d already read. The issue affected both mobile (DiscourseHub) and desktop users, persisted after refreshes for some, and was not resolved by safe mode. Initial suspicion fell on caching, but deeper investigation by Moin and others traced it to a recent CSS change in PR #34138, which removed the .latest-topic-list-item.visited selector affecting styling in /categories. The bug was confirmed to be more visible when logged in, as anonymous users had different styling rules. A temporary workaround using custom CSS was suggested. jordan.vidrine acknowledged the issue and fixed it in PR #34225. Users confirmed the fix restored normal read/unread visual cues. soegaard confirmed everything was back to normal after the patch.
Not a biggie, but I’m curious — has something changed here cachewise or something else?
iPad and DiscourseHub — when I open a topic from /latest, read it and go back swiping from left, that topic still shows as fresh, I mean it stays black, not turning to grey’ish.
That has been a bit unreliable always, but earlier opened topic wouldn’t change its ”status” perhaps one time of 10, but now every topic looks like not opened when coming back to /latest.
edit
Something has defenetly changed. Now every topic is black, and I don’t see what I’ve red or not. I move this to Contribute > UX
I saw that too when you posted. But after a reload everything is fine again. I think sometimes small changes in Discourse updates cause this until you reload the app so all the code running in your browser is up to date.
I know some weeks ago the avatars on latest were giant until I refreshed.
I think this is the issue somehow. I just tried your site and it’s fine logged out, made an account and it’s not working (my site can’t be read logged out so I tried yours )
), not caches.
