Browser history issue when the home page is not "Latest"

AI-generated summary

A browser history issue has been reported when the home page is not set to “Latest”. To reproduce the issue:

  1. Visit a Discourse website with a non-“Latest” home page, such as Funcom.
  2. Navigate to the “Latest” page via the hamburger menu.
  3. Click the top-left icon to return to the home page.
  4. Click the browser Back button, which does not redirect to the “Latest” page as expected.

Multiple users have confirmed this issue, including Dannii and tshenry. tshenry notes that a second click of the back button will redirect to the “Latest” page, but acknowledges it as a bug. The issue has been assigned to vinothkannans and is likely related to a previous bug fix regarding filter clearing. The issue has since been fixed in this commit.

How to reproduce:

  1. Go to a Discourse website where the landing page is not “Latest”, for example Funcom.
  2. From the home page, click Hamberger menu > Latest :right_arrow: this gets you to the “Latest” page.
  3. Click the top left Funcom icon :right_arrow: this gets you back to the home page.
  4. Click the browser Back button :right_arrow: nothing happens. Expected result: you go back to “Latest”.
3 Likes

Can you repro this @tshenry?

I can confirm this on https://intfiction.org/

2 Likes

I can repro this, but it’s fairly new. I have a self-install site currently running v2.3.0.beta5 +5 where this doesn’t happen. It seems to have been added somewhere in this set of commits.

A second click of the back button will go back to latest, but this is definitely a bug.

5 Likes

Aha we should assign this to someone @zogstrip

1 Like

@vinothkannans can you bump this to the top of your list.

Likely a result of the other related bug fix regarding filter clearing?

4 Likes

It is fixed in

https://github.com/discourse/discourse/commit/0861ca7764d37f5b5a2472a54306cc71b58a961e

7 Likes

This topic was automatically closed after 5 days. New replies are no longer allowed.