We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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 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.
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
Signal Version:
6.2.0 production
Operating System:
Windows 11 pro
Linked Device Version:
Android
https://debuglogs.org/desktop/6.2.0/938be471d8c0b0163fac41671bee8304c42eb9bd1891ceb29494dffb21f4a14e.gz
The text was updated successfully, but these errors were encountered:
Fix flaky search behaviour with minimized left pane (fixes signalapp#…
8bb3686
…6255)
ad22fd6
Successfully merging a pull request may close this issue.
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
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
The text was updated successfully, but these errors were encountered: