RocketChat / RocketChat/Rocket.Chat
fix: The back and forward buttons in the navbar are not getting disabled even if being in the last or first page
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description
The Back and Forward buttons in the navbar are not getting disabled when the user reaches the first or last page in the navigation history.
Both buttons remain clickable even when there is no previous or next page available in the history stack.
Steps to Reproduce
Open Rocket.Chat in the browser.
Navigate between different pages (e.g., Home → Channel A → Channel B).
Click the Back button until you reach the first page.
Observe that the Back button is still enabled.
Click the Forward button until you reach the last page.
Observe that the Forward button is still enabled.
Expected Behavior
The Back button should be disabled when the user is on the first page in the navigation history.
The Forward button should be disabled when the user is on the last page in the navigation history.
The buttons should dynamically update based on available navigation history.
Actual Behavior
The Back and Forward buttons remain enabled even when no navigation is possible in that direction.
Clicking them does not perform any action, but they still appear active.
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 reproducing the issue in Rocket.Chat in a browser, following the navbar Back and Forward controls through a navigation history such as Home → Channel A → Channel B. Trace how the controls determine whether previous or next pages exist; done means each button dynamically appears disabled at the corresponding history boundary and remains usable otherwise.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100