mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #5449] [feature]: Collapse sidebar on dragging beyond min width #2094
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#2094
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Sockalingam29 on GitHub (Oct 5, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5449
Originally assigned to: @Sockalingam29 on GitHub.
Is there an existing issue for this?
Summary
Currently, the sidebar can only be closed by clicking the collapse button in the bottom-right corner. When resizing the sidebar by dragging, it stops shrinking once it reaches the minimum width. A better experience would be to automatically close the sidebar if the user drags it past this minimum width.
Why should this be worked on?
On smaller laptop screens, users often prefer to keep the sidebar closed to maximize workspace. When I first tried to close it, my instinct was to drag the sidebar all the way in, but it stopped at the minimum width. It took me a moment to realize that I had to use the collapse button instead.
I can work on this feature if we’re aligned on the approach.
@nivedin commented on GitHub (Oct 6, 2025):
The approach looks good, assigning this to you 👍🏼
@techieadi4703 commented on GitHub (Oct 6, 2025):
@nivedin @abraham @Sockalingam29 @silentmatt I'm interested in this issue can you assign me this issue to me.
@liyasthomas commented on GitHub (Oct 6, 2025):
Feel free to give it a try @techieadi4703.
@Sockalingam29 commented on GitHub (Oct 6, 2025):
Working on this
@Sockalingam29 commented on GitHub (Oct 19, 2025):
I noticed a PR already created for this issue after I was assigned, so I've paused my work on this. Let me know if I still need to look into this.
If the PR is moving forward, please unassign me from this issue.