You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When resizing the browser window while a thread is open in a channel, the thread panel takes up the entire screen, but the sidebar remains open, overlapping the content.
Steps to reproduce:
Open Rocket.Chat in a browser.
Resize the browser window to about half the screen width.
Open a thread in any channel.
Gradually reduce the browser width further.
Observe that at a certain point, the thread panel expands to take the full screen while the sidebar remains visible.
Expected behavior:
When the thread panel takes full screen on small window sizes, the sidebar should automatically collapse to ensure a clean layout.
Actual behavior:
The thread panel takes up the entire screen, but the sidebar remains open, causing an overlap and layout issues.
Server Setup Information:
Version of Rocket.Chat Server: open.rocket.chat
Client Setup Information
Desktop App or Browser Version:firefox 136.0.1 (64-bit)
Operating System:Ubuntu 24.04.2 LTS
Additional context
side.bar.issue.rc.mp4
If anyone wants to work on this issue, feel free to open a PR. Contributions are welcome, and the first valid PR will be considered. Thank you!
The text was updated successfully, but these errors were encountered:
Description:
When resizing the browser window while a thread is open in a channel, the thread panel takes up the entire screen, but the sidebar remains open, overlapping the content.
Steps to reproduce:
Expected behavior:
When the thread panel takes full screen on small window sizes, the sidebar should automatically collapse to ensure a clean layout.
Actual behavior:
The thread panel takes up the entire screen, but the sidebar remains open, causing an overlap and layout issues.
Server Setup Information:
Client Setup Information
Additional context
side.bar.issue.rc.mp4
If anyone wants to work on this issue, feel free to open a PR. Contributions are welcome, and the first valid PR will be considered. Thank you!
The text was updated successfully, but these errors were encountered: