Split topic posts appearing as not having been visited

[SlyRemarks (Gwil OpenEnergyMonitor)]

A very minor issue we have noticed on our self-hosted Discourse (v1.8.0.beta5 +33) - the issue described in the following topic is still occurring for us (posts that have been split are appearing as not having being visited):

"USER split this topic" makes topic forever "un-visited"

This topic got off-topic, so I split the the posts to a new topic. [image] Here you can see the new topic is greyed out with class="title visited" because I’ve read it all. The parent topic is still black, with class="title" [image] Doesn’t matter how many times I go into the parent topic to read it, it remains black in the Latest view. This is the case with any topic that’s had posts forked to a new topic. Here’s an old one: [image] However, if I delete the “user split this topic” post…

It doesn’t always behave this way. A topic that I split would not appear “grayed” out to me (an Admin), but it did to another Admin. Moderators have reported the same thing.

[david (David Taylor)]

We see the same issue on our forum (running latest).

It only seems to happen if the last post on a topic is deleted/split/moved. A workaround is to just make another post on the topic, but that’s left us with a lot of posts that look something like

making a random post to mark topic read

which is clearly not ideal.

[Remah (Just another happy Discourse user)]

Have the same problem. It has minor impact but it is perpetually annoying on every Latest view.

The problem arose when I split a topic as also reported in:

Split topics don't get "read" styling in list

I believe this is related to: The topic doesn’t show up in my “unread” list, but it doesn’t get the “read” styling in the list – that is, its title is still displayed in black, rather than the expected light grey. It’s not a major issue, but it does make the inbox-zero perfectionist in me twitch.

However, I didn’t have this problem when I split a topic week earlier.

This was apparently fixed so it might be a regression:

"USER split this topic" makes topic forever "un-visited"

This is now fixed in latest courtesy of @sam

[Remah (Just another happy Discourse user)]

The only difference that I can think of between the two split topics - apart from the different dates - is that the working split topic had only one post selected whereas the topic with this bug had two posts selected to create the new topic.