Direct answer
The short version
When you go Back and then navigate to a new location, a browser-style history normally discards the old Forward entries and records the new destination instead. Forward is not a permanent archive; it is the route back toward the newest point on the currently selected trail.
Key takeaways
- Back and Forward represent one active path, not a tree-shaped archive.
- A new move after Back replaces the abandoned Forward branch.
- Selecting an existing entry should move the cursor; capturing a new location should create the branch.
- Save important destinations separately before exploring from an older point.
A simple three-location example
Visit A, then B, then C. Back moves from C to B, while C becomes available through Forward. If you now navigate from B to D, the active trail becomes A, B, D. C is no longer the Forward destination.
This behavior makes the controls predictable: Forward reverses recent Back movement, while new navigation expresses a different intent and creates a different latest route.
- Initial trail: A → B → C.
- After one Back: A → B, with C ahead.
- New navigation to D: A → B → D.
- Result: C is no longer on the active Forward path.
Why browsers and cross-app histories use this model
A linear stack makes Back and Forward understandable without asking which branch to follow. Browsers expose session history through a current entry plus traversal methods, and web apps can add or replace entries.
ReturnFast follows the same mental model across app locations. Consecutive duplicate states are suppressed so moving through the trail represents meaningful context changes rather than repeated observations of one window.
Preserve an old destination before creating a branch
If C matters beyond the immediate trail, save it in the system that owns it: bookmark a URL, pin or name a tab, save a workspace, note a file path, keep a reproducible command, or record a source in project notes.
Recent navigation optimizes return. Durable references preserve knowledge. Treat Forward as a convenient reversal, not the only record of a valuable destination.
Recognize the branch point
Notice when you have moved Back and are about to go somewhere new.
Save anything durable
Bookmark, note, pin, or commit the destination that must not be lost.
Create the new route
Navigate normally once the prior value has a durable home.
Further reading and product details
Frequently asked questions
Why did my Forward button become disabled?
You likely navigated to a new location after going Back, which replaced the old Forward branch with a new active route.
Can I recover the discarded branch?
Not through the active Forward stack. Use browser History, recent files, search, project notes, or another durable record owned by the destination app.
Does Back history store every repeated state?
A useful implementation should deduplicate consecutive equivalent states so one location does not create many redundant stops.