Read topics look like un-read, when going back to latest

UX
1

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 UX

1 Like
2

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.

3

Yeah. Closing the hub and opening again was a fix indeed. I blame cache :joy:

1 Like
4

I think this was related to UX: Fix old syntax (#34138) · discourse/discourse@f6a1648 · GitHub (a very mysterious commit message @jordan.vidrine :grinning_face:), not caches.

Thanks for the report, though!

3 Likes
5

FWIW - we are seeing the same issue at https://racket.discourse.group/

1 Like
6

Hi We are still seeing this - closing / refreshing the tab does not resolve this.

7

Does safe mode help?

8

Mine is still doing too after endless reloads on desktop

9

This topic was automatically closed after 17 hours. New replies are no longer allowed.

11

@jordan.vidrine any ideas?