mirror of
https://github.com/BoostIO/BoostNote-App.git
synced 2026-04-27 05:15:56 +03:00
[GH-ISSUE #764] Navigation menu buttons are not useful when collapsed #397
Labels
No labels
android 🤖
assigned to core 🦹
bug 🐛
documentation 📚
documentation 📚
duplicate 🚫
external issue 🔼
external issue 🔼
feature request 🌟
funded on issuehunt 💵
help wanted 🆘
improvement request 🔨
improvement request 🔨
ios 🍎
mobile 📱
needs investigation 🔬
needs more info ℹ️
needs specs 📐
plugin idea 🔌
plugin idea 🔌
poll 🗳️
pull-request
question ❓
rewarded on issuehunt 🎁
security issue 🔑
won’t fix ❌
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/BoostNote-App#397
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 @Komediruzecki on GitHub (Jan 11, 2021).
Original GitHub issue: https://github.com/BoostIO/BoostNote-App/issues/764
Current behavior
The buttons are not usable when there is no space in the navigation menu.
See image:

Expected behavior
The buttons should either be useful or not shown if they cannot be used in such a tight space.
Steps to reproduce
Environment
Desktop
@Rokt33r commented on GitHub (Aug 20, 2021):
@Komediruzecki The bug is still existing in v0.21.1. But I'm not how should we deal with this issue. Should we hide all buttons and show the three dots button only? Do you have any other idea?
@Komediruzecki commented on GitHub (Aug 20, 2021):
@Rokt33r I don't think the bug is still there in latest version.
The buttons actually work and the minimum space on new sidenav actually makes them clickable just fine.
I'll see if we want to hide them if there is no clear space to show everything and also the full label.
@Rokt33r commented on GitHub (Aug 23, 2021):
That's what I meant. But I'll close this issue since it is a quite minor issue and the original issue has been fixed already.