Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If sidebar is at its thinnest state, activating search makes it so you cannot go back to lowest width #6255

Open
2 tasks done
dsoh opened this issue Jan 23, 2023 · 0 comments · May be fixed by #6817
Open
2 tasks done
Labels

Comments

@dsoh
Copy link

dsoh commented Jan 23, 2023

  • I have searched open and closed issues for duplicates
  • I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Bug Description

If you make the chat list to its thinnest width by resizing the left side bar, and hit ctrl f the side bar will appear and set to a certain size.

once in this state you cannot resize the sidebar back to minimal state until completely quitting and reopening signal.

Steps to Reproduce

  1. resize sidebar to smallest state
  2. hit ctrl + f to focus the search
  3. try to resize the sidebar to the smallest state again.

Actual Result:

the sidebar's minimal width is now stuck at the initial width that ctrl f resized to

Expected Result:

the side bar should be resizable back to the smallest state

Screenshots

Platform Info

Signal Version:

6.2.0 production

Operating System:

Windows 11 pro

Linked Device Version:

Android

Link to Debug Log

https://debuglogs.org/desktop/6.2.0/938be471d8c0b0163fac41671bee8304c42eb9bd1891ceb29494dffb21f4a14e.gz

smably added a commit to smably/Signal-Desktop that referenced this issue Mar 9, 2024
smably added a commit to smably/Signal-Desktop that referenced this issue Mar 9, 2024
@smably smably linked a pull request Mar 9, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging a pull request may close this issue.

2 participants