nextcloud / nextcloud/cookbook
Sort/keyword filter buttons stop working below 1024px viewport width
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 641
- Forks
- 113
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 26
Description
Title: Sort/keyword filter buttons stop working below 1024px viewport width
Bug description
The sort button (alphabetical ascending/descending) and the keyword filter stop working as soon as the window width drops below 1024px — the threshold where the left navigation sidebar collapses/disappears.
Steps to reproduce
- Open Cookbook on a screen ≥1024px wide — sort and keyword filter work normally
- Reduce the window width below 1024px (or use Chrome DevTools responsive mode)
- Click the sort button or a keyword filter
- Nothing happens — no error in the console
Expected behavior
Sort/filter should work regardless of screen width.
Reproducibility
- Confirmed on PC (Chrome DevTools responsive mode, without even reloading the page)
- Confirmed on Android tablet (Galaxy Tab A11+, Chrome, up to date)
- Confirmed on Android phone (Pixel 7, Chrome, up to date)
- Confirmed on Edge desktop as well — same behavior
- Works normally as soon as the window goes back above 1024px, without reload
- No JavaScript console errors at any width
Environment
- Nextcloud: Hub 26 Spring (34.0.3)
- Cookbook: 0.11.10
- Browsers tested: Chrome desktop, Edge desktop, Chrome Android — identical behavior across all three
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
Start by reproducing the issue in Chrome DevTools responsive mode, checking the sort and keyword filter behavior above and below the 1024px breakpoint without reloading. Trace the responsive navigation/sidebar transition and the event handling for both controls; done means both actions work consistently at every tested width without console errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100