Using {location: 'replace'} to go back to the previous state should pop history instead of creating two identical entries

[imgx64]

Here's an example plunker (launch the preview in a separate window to see the history).

1. The app starts at state0. History is /state0.
2. Press the button to go to state1. History is /state0, /state0/state1.
3. Press the button to go to state2. History is /state0, /state0/state1, /state0/state1/state2.
4. Press the Go back button (which uses {location: 'replace'}) to go back to state1. History is now /state0, /state0/state1, /state0/state1, with duplicate /state0/state1.

I think a better behavior is to remove the duplicate state from history when this happens. The current behavior breaks the browser back button (now you have to click back twice to go back to state0).

[elitastic]

+1

[jvjvjv]

+2

[nateabele]

Our current handling of history is not very sophisticated. If you feel like working on a PR, let me know. Here, I already got you started: http://plnkr.co/edit/DJH6mQUCbTFfSbdCBYUo?p=preview

[mrtnjln]

Any news on this ?

[IainCole]

Should a state transition ever assume a "back" operation?

[bbaia]

+1

[Clomo]

👍

[netsurfergit]

👍

[stale]

This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs.

This does not mean that the issue is invalid. Valid issues
may be reopened.

Thank you for your contributions.