Navigation closes when clicking on board
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Describe the bug
Previously, the navigation sidebar (on the left side) would stay open unless explicitly closed.
This apparently changed either with NC 31 or with the latest Deck Version: When clicking on a board in the navigation, the navigation closes.
To Reproduce
Steps to reproduce the behavior:
- Open the navigation
- Click on a board
- Board is opened but navigation closes
Expected behavior
The navigation should not close unless explicitly closed.
Client details:
- OS: W11
- Browser: Firefox
- Version: 135
- Device: desktop
Server details
Operating system: Debian Bookworm
Web server: nginx
Database: psql
PHP version: 8.2.26
Nextcloud version: 31.0.0
Where did you install Nextcloud from: tar.gz
Signing status:
Login as admin user into your Nextcloud and access
http://example.com/index.php/settings/integrity/failed
paste the results here.
List of activated apps:
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder
Nextcloud configuration:
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
or
Insert your config.php content here
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
Logs
Nextcloud log (data/nextcloud.log)
Insert your Nextcloud log here
Browser log
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Reproduce the issue by opening the navigation and clicking a board, then trace the navigation and board-opening entry points to identify where the sidebar is closed. Done means the board opens while the navigation remains open unless explicitly closed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100