RocketChat / RocketChat/Rocket.Chat
Mobile UI Regression: Sidebar does not autoclose, cannot be swiped closed
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:
Sidebar should autoclose upon room join, and menu should be swipeable from anywhere.
Steps to reproduce:
- Be on a small screen or mobile device where the sidebar is not permanently visible.
- Open sidebar.
- Click channel.
- You must now close it manually. Try to swipe within the boundary of the sidebar, does not work. Click on the room overlay itself (right side) - that works.
Expected behavior:
Swipe to close anywhere, or click to close on room name in list.
Actual behavior:
- Cannot swipe from within the sidebar, but tapping or swiping from outside it (on top of room) works
- Clicking on a room link does not close the sidebar, you have to close it yourself
Server Setup Information:
- Version of Rocket.Chat Server: 3.11.0-develop
- Operating System: ContainerOS
- Deployment Method: Docker
- Number of Running Instances: Scalable
- DB Replicaset Oplog: -
- NodeJS Version: 14
- MongoDB Version: Atlas
Client Setup Information
- Desktop App or Browser Version: Any small screen or mobile
- Operating System: Any
Additional context
None
Relevant logs:
None
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
No file or test is named. Start by reproducing the sidebar behavior on a small screen: open the sidebar, join a channel, and try swiping within its boundary and tapping the room area. Done means joining a room closes the sidebar and swiping from within it closes the menu.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100