RocketChat / RocketChat/Rocket.Chat
Clicking a username on sidebar makes chat reload on mobile (NOT APP)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
When you click a username on the left sidebar the sidebar closes, and the window reloads. This also happens on opne.rocket.chat. This also prevents the usage of the sub menu on the sidebar to hide, etc the chat in question.
Steps to reproduce:
- Attempt to open a private chat or room on the left sidebar when using mobile device such as iphone.
- Rocket chat reloads and bring you to the room, using the sub menu to hide, etc is impossible.
Expected behavior:
For the sidebar list of chats open to function correctly and allow for the use of the sub menu. For rocketchat to not reload.
Actual behavior:
Rocketchat reloads and does not allow you to use the sub menu for the chat in question.
Server Setup Information:
- Version of Rocket.Chat Server: 4.6.3
- Operating System: Centos 7
- Deployment Method: tar
- Number of Running Instances: 12
- DB Replicaset Oplog: yes
- NodeJS Version: 4.18.3
- MongoDB Version:4.02
Client Setup Information
- Desktop App or Browser Version: Browser IOS
- Operating System: IOS Mobile
Additional context
Relevant logs:
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 sidebar username or room selection in an iOS mobile browser and observe the reload and submenu behavior. Trace the mobile sidebar navigation entry point to identify why selecting a chat reloads the window. Done means the chat opens without a reload and its submenu remains usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100