Update unread counters after keyboard navigation

ux
1

Let’s walk through a simple read workflow:

  1. Start at Latest.
  2. Using the mouse, navigate into a tracked topic. Read the topic.
  3. Using the mouse, navigate back to the Latest index by clicking on the logo at the top of the page.

When navigating with the mouse in this way, Discourse will automatically update the unread counters alongside the topic titles in the index.

Now repeat with keyboard navigation:

  1. Start at Latest.
  2. Using the keyboard (J, K, and RETURN), navigate into a tracked topic. Read the topic.
  3. Using the keyboard, strike the U key to return to the Latest index.

In this latter case, the unread counters are not automatically updated.

This feels like a case of cache incoherency. Is it fixable?

2 Likes
2

Isn’t this the same as using the back button in the browser? Try it and see. I don’t think keyboard is the relevant bit here.

1 Like
3

Do you get the same result if you return to latest with “gl”?

4

On second look, this does not appear to be reliably reproducible. Unread counters are updated and redrawn on some occasions. This is clearly not a UX problem. I’ll close out this topic and see if I can hone in on the conditions under which it does not work as expected. My apologies for the noise.