# Back is not always taking me to the correct page
**URL:** https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286
**Category:** Bug
**Created:** [2월 16, 2015, 12:24오후 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286 "2015-02-16T12:24:27Z")
**Posts on this page:** 18
**Page:** 1
### Author:  [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [2월 16, 2015, 12:24오후 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/1 "2015-02-16T12:24:28Z")
Okay, I don’t think this is just me any more. I’ve been having this odd experience on mobile and on a desktop for a few days now here at Meta.
Whenever I use the back button on my mobile (Android using Chrome) or if I use the u shortcut on a desktop, I’m occasionally taken to the wrong page (think 2 pages in my history instead of 1 page back in my history).
I don’t have easily reproducible steps other than, use it for a while and see what happens, but here is my typical workflow that causes it (after you use it for a while)
1. Navigate to Latest
2. Click on a topic
3. Read topic, press u
4. You should be back to latest
5. Click on the same topic you just read
6. Press u
7. You should be back to latest (but you might not be)
8. Click on a different topic
9. Perform steps 3-8 again until issue occurs.
---
### Author:  [@elberet](https://meta.discourse.org/u/elberet)
#### Post date: [2월 16, 2015, 1:32오후 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/2 "2015-02-16T13:32:53Z")
The same thing is occasionally happening to me, too, except with my mouse’s back button rather than the u shortcut key.
---
### Author:  [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [2월 16, 2015, 1:33오후 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/3 "2015-02-16T13:33:53Z")
Awesome, then it isn’t just me 😄
---
### Author:  [@elberet](https://meta.discourse.org/u/elberet)
#### Post date: [2월 16, 2015, 1:37오후 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/4 "2015-02-16T13:37:08Z")
No, it’s not just you, and this isn’t the first time it’s came up:
[https://meta.discourse.org/t/back-forward-back-forward-does-not-seem-to-work-right/18034](https://meta.discourse.org/t/back-forward-back-forward-does-not-seem-to-work-right/18034)
[https://meta.discourse.org/t/back-button-after-posting-does-not-go-back/9829](https://meta.discourse.org/t/back-button-after-posting-does-not-go-back/9829)
[ ](https://www.youtube.com/watch?v=CRpz0zuAGVs&t=4m4s)
---
### Author:  [@TechnoBear](https://meta.discourse.org/u/TechnoBear)
#### Post date: [2월 16, 2015, 2:18오후 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/5 "2015-02-16T14:18:25Z")
I’ve also been experiencing the same thing, but you know me - I’ve just been assuming I must have done something wrong. Nice to know I’m not alone here after all.
---
### Author:  [@purldator](https://meta.discourse.org/u/purldator)
#### Post date: [2월 16, 2015, 3:07오후 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/6 "2015-02-16T15:07:39Z")
Adding more voices that it has happened to me as well. Intermittent but enough to remember. Didn’t know if it was just me or if the Matrix is actually having a glitch, heh.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2월 16, 2015, 8:18오후 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/7 "2015-02-16T20:18:50Z")
yeah … this still happens sometimes.
---
### Author:  [@JSey](https://meta.discourse.org/u/JSey)
#### Post date: [2월 16, 2015, 8:31오후 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/8 "2015-02-16T20:31:13Z")
Phew - glad it isn’t just me… strange!
---
### Author:  [@danwad](https://meta.discourse.org/u/danwad)
#### Post date: [2월 16, 2015, 10:52오후 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/9 "2015-02-16T22:52:00Z")
Getting this quite often when backing out of a topic and expecting to go to the latest page but goes to a previously read topic. Chrome on Android.
---
### Author:  [@jaming](https://meta.discourse.org/u/jaming)
#### Post date: [2월 17, 2015, 12:40오전 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/10 "2015-02-17T00:40:16Z")
> [@danwad](#):
>
> Getting this quite often when backing out of a topic and expecting to go to the latest page but goes to a previously read topic
Same on Windows Phone 8.1. It never was this bad before.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2월 17, 2015, 4:15오전 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/11 "2015-02-17T04:15:59Z")
Does anyone have a repro?
---
### Author:  [@jaming](https://meta.discourse.org/u/jaming)
#### Post date: [2월 17, 2015, 5:00오전 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/12 "2015-02-17T05:00:14Z")
I can repo this on my Win 8.1 Desktop using IE11 & Chrome. I don’t think the problem is contained to this, but the easiest way to repo this is to quickly hit the back button after entering a topic. You will go back to the topic list and after less than a second the url will be update from /latest to the url for topic you were just loaded even though you are on the latest view.
---
### Author:  [@Mittineague](https://meta.discourse.org/u/Mittineague)
#### Post date: [2월 17, 2015, 5:07오전 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/13 "2015-02-17T05:07:52Z")
Confirmed Firefox latest Windows7
Though I had to “force” it as this has never naturally happened to me
From latest click on topic
_before_ the topic loads, click back
Address bar updates to topic URL although really on Latest
Click on a topic letting it load
Click back
Goes to URL that was in address bar
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2월 17, 2015, 5:18오전 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/14 "2015-02-17T05:18:03Z")
Since we have a repro perhaps you can look at this @eviltrout?
---
### Author:  [@dkf](https://meta.discourse.org/u/dkf)
#### Post date: [2월 17, 2015, 8:37오후 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/15 "2015-02-17T20:37:43Z")
> [@codinghorror](#):
>
> Does anyone have a repro?
I’ve been seeing this fairly frequently for a week or two (Chrome, just a bit behind current, OSX) but _not_ every time I go back a page. Just enough times a day to be really annoying. If I ever figure out how to get a reliable reproduction I’ll say more.
---
### Author:  [@accalia](https://meta.discourse.org/u/accalia)
#### Post date: [2월 17, 2015, 8:52오후 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/16 "2015-02-17T20:52:17Z")
can reproduce using backspace on desktop chrome.
usually it’s when the site’s acting sluggish (not sure if on my end or remote, or if it makes a difference)
---
### Author:  [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [2월 17, 2015, 9:26오후 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/17 "2015-02-17T21:26:07Z")
I’ve got a fix baking in master right now, thanks for the help reporting/reproducing it:
[https://github.com/discourse/discourse/commit/762e60c0a6e8fe1468769b7209019ccf7f8f4808](https://github.com/discourse/discourse/commit/762e60c0a6e8fe1468769b7209019ccf7f8f4808)
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2월 17, 2015, 10:37오후 UTC](https://meta.discourse.org/t/back-is-not-always-taking-me-to-the-correct-page/25286/18 "2015-02-17T22:37:23Z")