[GH-ISSUE #1674] [FR] Auto-hide sidebar when re-sizing the window #641

Closed
opened 2026-03-23 20:39:05 +00:00 by mirror · 17 comments
Owner

Originally created by @richardshiue on GitHub (Jan 6, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/1674

Originally assigned to: @Shreesh09 on GitHub.

Description

It would be nice if the sidebar can automatically hide when the window shrinks to the point that the sidebar becomes floating.

Impact

Users who resize their AppFlowy window to a small size

Additional Context

No response

Originally created by @richardshiue on GitHub (Jan 6, 2023). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/1674 Originally assigned to: @Shreesh09 on GitHub. ### Description It would be nice if the sidebar can automatically hide when the window shrinks to the point that the sidebar becomes floating. ### Impact Users who resize their AppFlowy window to a small size ### Additional Context _No response_
Author
Owner

@onyicodes commented on GitHub (Jan 17, 2023):

Hi @richardshiue can you provide more details on this. An image showing the current state will be helpful.
Thanks

<!-- gh-comment-id:1386044201 --> @onyicodes commented on GitHub (Jan 17, 2023): Hi @richardshiue can you provide more details on this. An image showing the current state will be helpful. Thanks
Author
Owner

@richardshiue commented on GitHub (Jan 19, 2023):

@onyicodes Sure. This is the current behavior. It'd be better if the sidebar could automatically hide when the window becomes small enough.

https://user-images.githubusercontent.com/71320345/213331256-376f1d31-1eb1-48fb-b1a2-bf6415e48b58.mp4

<!-- gh-comment-id:1396309622 --> @richardshiue commented on GitHub (Jan 19, 2023): @onyicodes Sure. This is the current behavior. It'd be better if the sidebar could automatically hide when the window becomes small enough. https://user-images.githubusercontent.com/71320345/213331256-376f1d31-1eb1-48fb-b1a2-bf6415e48b58.mp4
Author
Owner

@onyicodes commented on GitHub (Jan 19, 2023):

Okay thanks. I have a clear picture of what is required now. Please can you assign this to me?

<!-- gh-comment-id:1396389786 --> @onyicodes commented on GitHub (Jan 19, 2023): Okay thanks. I have a clear picture of what is required now. Please can you assign this to me?
Author
Owner

@onyicodes commented on GitHub (Jan 19, 2023):

@richardshiue Which would be better?
The sidebar closes when the window is small enough and reappears when the window is expanded beyond a certain extent or it does not reappear automatically but waits for user to tap on open sidebar icon again?

<!-- gh-comment-id:1396395424 --> @onyicodes commented on GitHub (Jan 19, 2023): @richardshiue Which would be better? The sidebar closes when the window is small enough and reappears when the window is expanded beyond a certain extent or it does not reappear automatically but waits for user to tap on open sidebar icon again?
Author
Owner

@richardshiue commented on GitHub (Jan 20, 2023):

Please can you assign this to me?

Sure! I've assigned it to you. Thank you for helping with this.

@richardshiue Which would be better?

Ideally, this is the UX I'm accustomed to. If the sidebar was hidden when the window was still large enough (before shrinking the window), then the latter. If the sidebar was shown, then the former. You can absolutely just choose one for now and alter the behavior later on.

<!-- gh-comment-id:1397838758 --> @richardshiue commented on GitHub (Jan 20, 2023): > Please can you assign this to me? Sure! I've assigned it to you. Thank you for helping with this. > @richardshiue Which would be better? Ideally, this is the UX I'm accustomed to. If the sidebar was hidden when the window was still large enough (before shrinking the window), then the latter. If the sidebar was shown, then the former. You can absolutely just choose one for now and alter the behavior later on.
Author
Owner

@onyicodes commented on GitHub (Jan 20, 2023):

Please can you assign this to me?

Sure! I've assigned it to you. Thank you for helping with this.

@richardshiue Which would be better?

Ideally, this is the UX I'm accustomed to. If the sidebar was hidden when the window was still large enough (before shrinking the window), then the latter. If the sidebar was shown, then the former. You can absolutely just choose one for now and alter the behavior later on.

Alright. Thanks

<!-- gh-comment-id:1398833986 --> @onyicodes commented on GitHub (Jan 20, 2023): > > Please can you assign this to me? > > Sure! I've assigned it to you. Thank you for helping with this. > > > @richardshiue Which would be better? > > Ideally, this is the UX I'm accustomed to. If the sidebar was hidden when the window was still large enough (before shrinking the window), then the latter. If the sidebar was shown, then the former. You can absolutely just choose one for now and alter the behavior later on. Alright. Thanks
Author
Owner

@huang12zheng commented on GitHub (Feb 4, 2023):

Compact Width < 600
Medium 600 < width < 840
Expanded Width > 840
Could be a possible reference value?
@onyicodes

<!-- gh-comment-id:1416673543 --> @huang12zheng commented on GitHub (Feb 4, 2023): Compact Width < 600 Medium 600 < width < 840 Expanded Width > 840 Could be a possible reference value? @onyicodes
Author
Owner

@onyicodes commented on GitHub (Feb 7, 2023):

Compact Width < 600 Medium 600 < width < 840 Expanded Width > 840 Could be a possible reference value? @onyicodes

Noted.
I'm already using less than 600 as compacted, while above 600 is expanded

<!-- gh-comment-id:1420490333 --> @onyicodes commented on GitHub (Feb 7, 2023): > Compact Width < 600 Medium 600 < width < 840 Expanded Width > 840 Could be a possible reference value? @onyicodes Noted. I'm already using less than 600 as compacted, while above 600 is expanded
Author
Owner

@AmanNegi commented on GitHub (Mar 2, 2023):

Hey @onyicodes, are you working on this issue?

<!-- gh-comment-id:1451231033 --> @AmanNegi commented on GitHub (Mar 2, 2023): Hey @onyicodes, are you working on this issue?
Author
Owner

@onyicodes commented on GitHub (Mar 2, 2023):

Hi @AmanNegi yeah I'm still working on it.

<!-- gh-comment-id:1452585311 --> @onyicodes commented on GitHub (Mar 2, 2023): Hi @AmanNegi yeah I'm still working on it.
Author
Owner

@AmanNegi commented on GitHub (Mar 3, 2023):

Great! 💚

<!-- gh-comment-id:1452860774 --> @AmanNegi commented on GitHub (Mar 3, 2023): Great! 💚
Author
Owner

@annieappflowy commented on GitHub (Mar 9, 2023):

Let us know if you need help!

<!-- gh-comment-id:1461271507 --> @annieappflowy commented on GitHub (Mar 9, 2023): Let us know if you need help!
Author
Owner

@sshdopey commented on GitHub (Mar 15, 2023):

@onyicodes have you worked on this, I would be glad to help

<!-- gh-comment-id:1469603731 --> @sshdopey commented on GitHub (Mar 15, 2023): @onyicodes have you worked on this, I would be glad to help
Author
Owner

@onyicodes commented on GitHub (Mar 15, 2023):

Yeah @DestinedCodes I'm making some good progress. Thanks for asking

<!-- gh-comment-id:1469984414 --> @onyicodes commented on GitHub (Mar 15, 2023): Yeah @DestinedCodes I'm making some good progress. Thanks for asking
Author
Owner

@Shreesh09 commented on GitHub (Oct 9, 2023):

I would like to work on this issue

<!-- gh-comment-id:1752208937 --> @Shreesh09 commented on GitHub (Oct 9, 2023): I would like to work on this issue
Author
Owner

@richardshiue commented on GitHub (Oct 9, 2023):

I've assigned it to you, have fun coding~

<!-- gh-comment-id:1753072149 --> @richardshiue commented on GitHub (Oct 9, 2023): I've assigned it to you, have fun coding~
Author
Owner

@annieappflowy commented on GitHub (Nov 6, 2023):

Completed

<!-- gh-comment-id:1794021060 --> @annieappflowy commented on GitHub (Nov 6, 2023): Completed
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#641
No description provided.