# Posts from the topic I just left stay rendered in the next topic after in-app navigation

**URL:** https://meta.discourse.org/t/posts-from-the-topic-i-just-left-stay-rendered-in-the-next-topic-after-in-app-navigation/404488
**Category:** Bug
**Tags:** fixed, nested-replies
**Created:** [4 juni 2026 om 03:27 UTC](https://meta.discourse.org/t/posts-from-the-topic-i-just-left-stay-rendered-in-the-next-topic-after-in-app-navigation/404488 "2026-06-04T03:27:17Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![Andry\_Osminin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/andry_osminin/32/565957_2.png) [@Andry\_Osminin](https://meta.discourse.org/u/Andry_Osminin)
#### Post date: [4 juni 2026 om 03:27 UTC](https://meta.discourse.org/t/posts-from-the-topic-i-just-left-stay-rendered-in-the-next-topic-after-in-app-navigation/404488/1 "2026-06-04T03:27:18Z")

</div>

I enabled nested replies for all topics (Horizon theme) and hit a state bug I can now  
reproduce, on both mobile and desktop.

When I open a topic, read it, and then jump to another topic via the suggested/related  
topics block (so client-side navigation, no reload), replies from the topic I just left  
sometimes stay on screen — rendered nested under the first branch of the new topic.  
They even attach under a post that’s been deleted in the new topic. It doesn’t clear if  
I keep navigating to more topics; only a full page reload gets rid of it.

One important detail: it’s intermittent. The first hop through the related block is  
usually fine, and I can click through it several times with no problem. It only seems to  
show up after navigating through the related topics block two or more times in a row.

Steps to reproduce:

1. Open a topic with nested replies.
2. Open another topic through the suggested/related block (no reload), and keep doing  
this a few times in a row.
3. After two or more consecutive hops through the block, replies from a previous topic  
appear nested under the first branch of the current topic, sometimes under a post  
that is deleted there.
4. They persist across further in-app navigation until a hard reload.

There’s no JS error in the console, so I went into the Network tab, and it looks like the  
previous topic is simply never torn down:

- The inspected page is topic 724 (/n/vibriruet-pri-troganii…/724?sort=old).
- While I’m on 724, a request for the previous topic’s data is still in the log:  
509.json?sort=old&track\_visit=true.
- The live message-bus poll still has Referer …/n/pinki-tolchki-…-na-nissane-kube/509  
— i.e. topic 509’s message-bus subscription was never re-pointed at 724.

So it really seems like the nested route doesn’t reset the post stream / message-bus  
subscription of the topic you came from on client-side navigation. First noticed on  
mobile, but it behaves the same on desktop.

Discourse version: 2026.6.0-latest ([27f76aa897](https://github.com/discourse/discourse/commits/27f76aa897c9b9d780a7d90e608e43760e514766))  
Happy to attach a screen recording or dig further if that helps.

---

_[View the full topic](https://meta.discourse.org/t/posts-from-the-topic-i-just-left-stay-rendered-in-the-next-topic-after-in-app-navigation/404488)._