RocketChat / RocketChat/Rocket.Chat
Please Add ‘Go back’ action to NotFound page for improved navigation
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description
Currently, the NotFound page only provides a Homepage action.
This forces users to always navigate to /home, even when they reached the NotFound page from another internal route.
Adding a “Go back” action would improve navigation by allowing users to return to their previous page when applicable.
Why is this needed?
- Improves UX by respecting user navigation flow
- Reduces friction when users hit a NotFound route accidentally
- Common pattern in error / NotFound pages
Proposed behavior
- Add a Go back action on the NotFound page
- When navigation history exists, it should return to the previous page
- When no history exists, it should safely fall back to
/home
Scope
- UI-only change
- No breaking behavior
- Limited to NotFound page
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the NotFound page and its existing Homepage action in the TypeScript frontend. Verify navigation-history and direct-entry cases, then confirm that Go back returns to the previous page when possible and falls back to /home otherwise.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100