Users have reported an issue with the browser back button on topic lists, where a topic is not immediately marked as read after visiting it. loren and seanblue have reproduced the issue, noting that it takes two visits to mark a topic as read. Stephen mentions that this behavior is expected when using the browser back button, but navigating using the site logo or menu bar should work correctly. However, users have reported the issue occurring regardless of navigation method. codinghorror notes that the issue has been around for a while and is more pronounced when using the browser back button, and that @sam and @eviltrout are likely aware of it. The issue appears to be intermittent, as loren has reported difficulty reproducing it consistently.
We run a private instance but seeing the issue here too. It seems to take two visits to mark a topic as read.
Reproduction Steps:
Latest viewsObserve: The topic is still marked as unread, revisit and return to Latest will mark is as read.
AFAIK if you use the browser back button this is expected.
Navigating using the site logo or menu bar should work though.
I just visited this topic and then returned to latest, the topic was marked as read:
They both have the same issue
I had this issue earlier today on https://community.wanikani.com/ as well, at least on mobile. After visiting the new topic and navigating away, the title became grey as if it were read, but it still had the blue dot indicating it was unread.
@Stephen I don’t think I’ve ever seen this issue before, even when using the browser back button.
Reproducing appears to be intermittent on both meta and our gated community.
This one has been around a while, I am pretty sure @sam and @eviltrout are aware of it. Much more pronounced if you use the browser back button in my experience.
