I've confirmed this multiple times, but wanted to get some feedback here before creating a tracker.
It seems with the latest Chrome and/or vBulletin update, there is an issue with "back" in the browser when returning from a "new post" link. I've confirmed it both here at vB and on my own forum in Chrome. I have uninstalled and reinstalled Chrome multiple times. I have verified the issue does not exist in Edge.
To replicate the issue in Chrome (you'll need new posts/replies at your forum to test, or you can test it here at vB), here are the steps:
Thanks!
It seems with the latest Chrome and/or vBulletin update, there is an issue with "back" in the browser when returning from a "new post" link. I've confirmed it both here at vB and on my own forum in Chrome. I have uninstalled and reinstalled Chrome multiple times. I have verified the issue does not exist in Edge.
To replicate the issue in Chrome (you'll need new posts/replies at your forum to test, or you can test it here at vB), here are the steps:
- Use the "?goto=newpost" icon before the topic title on the left side.
- After being taken to the new post(s), attempt to return to the previous page with your back button.
- You should notice Chrome is choking on the "?..." and "#..." queries, and making it impossible to return to the previously viewed page... without multiple fast clicks (usually resulting in the wrong previous page) or physically choosing the previous page manually from the back button's drop down. (I use a mouse button for "back", but both routes react the same way)
Thanks!
Comment