# Prevent 'jumping out' and 'back in' when using notifications for the current topic

**URL:** https://meta.discourse.org/t/prevent-jumping-out-and-back-in-when-using-notifications-for-the-current-topic/18224
**Category:** Feature
**Created:** [2014年七月29日 17:07 UTC](https://meta.discourse.org/t/prevent-jumping-out-and-back-in-when-using-notifications-for-the-current-topic/18224 "2014-07-29T17:07:10Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![Matches](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@Matches](https://meta.discourse.org/u/Matches)
#### Post date: [2014年七月29日 17:07 UTC](https://meta.discourse.org/t/prevent-jumping-out-and-back-in-when-using-notifications-for-the-current-topic/18224/1 "2014-07-29T17:07:10Z")

</div>

If I am reading a topic but haven’t reached a post yet, I will get a blue notification in the top right corner. If I click on this notification, and click on the ‘goto’ link, I see what looks like a page refresh and then it goes to the topic post (that is sometimes one post below the one I was reading)

Proposal: Check if I’m in the topic I’m about to jump to. If I am, cancel the page refresh style navigation and use a page anchor jump (or similar) instead to prevent the page from refreshing. (This process might need to address your page loads though, it might have to be topic + current page for the anchor)

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2014年七月30日 00:38 UTC](https://meta.discourse.org/t/prevent-jumping-out-and-back-in-when-using-notifications-for-the-current-topic/18224/2 "2014-07-30T00:38:03Z")

</div>

Yes we definitely want to get this fixed, our in page router should be much smarter here.

It does get a bit tricky cause sometimes posts are in memory but not in DOM.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2014年七月30日 02:08 UTC](https://meta.discourse.org/t/prevent-jumping-out-and-back-in-when-using-notifications-for-the-current-topic/18224/3 "2014-07-30T02:08:33Z")

</div>

This should be trivial to tell based on the URL though.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2014年七月30日 02:09 UTC](https://meta.discourse.org/t/prevent-jumping-out-and-back-in-when-using-notifications-for-the-current-topic/18224/4 "2014-07-30T02:09:41Z")

</div>

Yeah I am going to look through the routing code.

---

<div class="post-metadata">

### Author: ![Matches](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@Matches](https://meta.discourse.org/u/Matches)
#### Post date: [2014年七月30日 14:17 UTC](https://meta.discourse.org/t/prevent-jumping-out-and-back-in-when-using-notifications-for-the-current-topic/18224/5 "2014-07-30T14:17:56Z")

</div>

Even with url auto change disabled?

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [2014年七月30日 17:29 UTC](https://meta.discourse.org/t/prevent-jumping-out-and-back-in-when-using-notifications-for-the-current-topic/18224/6 "2014-07-30T17:29:27Z")

</div>

Uh, yeah… it just needs to check the topic ID. The auto-change is for the post number.

---

<div class="post-metadata">

### Author: ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [2025年十二月4日 11:31 UTC](https://meta.discourse.org/t/prevent-jumping-out-and-back-in-when-using-notifications-for-the-current-topic/18224/7 "2025-12-04T11:31:08Z")

</div>


