github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-21 10:41:50 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

Filter panel on mobile is blocked and lacks a close (X) button #2333

New Issue
Closed
opened 2026-03-22 14:03:25 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-03-22 14:03:25 -05:00
Owner
Copy Link

Originally created by @Plong-Wasin on GitHub (Sep 11, 2025).

Description

When opening the filter panel on mobile screen sizes, the user is unable to interact with any elements because parts of the interface appear to be overlapped or blocked by either the top or bottom mobile browser UI. This makes it impossible to effectively use the filter controls.

Additionally, there is no close (X) button provided to easily close the filter panel on mobile, which would improve usability and user experience.

Issues observed:

  • Filter input and options are inaccessible or blocked by mobile browser UI elements.
  • No visible or intuitive way to close the filter overlay/panel once opened on mobile devices.

Suggested improvements:

  • Adjust the filter panel layout or positioning to prevent it from being obscured by mobile browser navigation/status bars.
  • Add a close (X) button prominently at the top of the filter panel to allow users to dismiss the filter view easily on mobile.

This issue was seen in screenshots from Android and iOS browsers, demonstrating the same blocking and lack of close control. Addressing these points will enhance usability for mobile users applying filters.

Vikunja Version

v1.0.0-rc1-128-e5e0413b

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

Image

Image

Image

Originally created by @Plong-Wasin on GitHub (Sep 11, 2025). ### Description When opening the filter panel on mobile screen sizes, the user is unable to interact with any elements because parts of the interface appear to be overlapped or blocked by either the top or bottom mobile browser UI. This makes it impossible to effectively use the filter controls. Additionally, there is no close (X) button provided to easily close the filter panel on mobile, which would improve usability and user experience. Issues observed: - Filter input and options are inaccessible or blocked by mobile browser UI elements. - No visible or intuitive way to close the filter overlay/panel once opened on mobile devices. Suggested improvements: - Adjust the filter panel layout or positioning to prevent it from being obscured by mobile browser navigation/status bars. - Add a close (X) button prominently at the top of the filter panel to allow users to dismiss the filter view easily on mobile. This issue was seen in screenshots from Android and iOS browsers, demonstrating the same blocking and lack of close control. Addressing these points will enhance usability for mobile users applying filters. ### Vikunja Version v1.0.0-rc1-128-e5e0413b ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots ![Image](https://github.com/user-attachments/assets/b4d9492a-20f4-4afa-a5a0-54a834ff8770) ![Image](https://github.com/user-attachments/assets/32b7c181-1397-42e6-8080-372b22a4e734) ![Image](https://github.com/user-attachments/assets/02e8c051-6c9a-4c10-8c46-e018414d74c8)
GiteaMirror commented 2026-03-22 14:03:27 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 11, 2025):

Do the buttons at the bottom appear when you scroll down?

@kolaente commented on GitHub (Sep 11, 2025): Do the buttons at the bottom appear when you scroll down?
GiteaMirror commented 2026-03-22 14:03:27 -05:00
Author
Owner
Copy Link

@Plong-Wasin commented on GitHub (Sep 11, 2025):

Sometimes (depending on the device/browser), it’s not possible to scroll down any further — the system seems to think the user is already at the bottom. Because of that, the bottom buttons never become visible or reachable.

In the video I attached, this happens on both iOS and Android using Chrome. On iOS specifically, when trying to scroll, there’s no scrolling animation at all, as if the panel is already fully scrolled, so the bottom part (including the buttons) cannot be accessed.

https://github.com/user-attachments/assets/71b58c3f-62db-4dea-88bd-7b621315cab7

https://github.com/user-attachments/assets/9322ac08-fbb8-457f-b705-a86d350adedf

@Plong-Wasin commented on GitHub (Sep 11, 2025): Sometimes (depending on the device/browser), it’s not possible to scroll down any further — the system seems to think the user is already at the bottom. Because of that, the bottom buttons never become visible or reachable. In the video I attached, this happens on both iOS and Android using Chrome. On iOS specifically, when trying to scroll, there’s no scrolling animation at all, as if the panel is already fully scrolled, so the bottom part (including the buttons) cannot be accessed. https://github.com/user-attachments/assets/71b58c3f-62db-4dea-88bd-7b621315cab7 https://github.com/user-attachments/assets/9322ac08-fbb8-457f-b705-a86d350adedf
GiteaMirror commented 2026-03-22 14:03:27 -05:00
Author
Owner
Copy Link

@Plong-Wasin commented on GitHub (Sep 11, 2025):

It might be related to the use of 100vh. On mobile browsers, 100vh doesn’t always account for the dynamic browser UI (address bar, navigation bar). Using 100dvh instead of 100vh could potentially fix the issue by properly adjusting for the visible viewport height.

@Plong-Wasin commented on GitHub (Sep 11, 2025): It might be related to the use of 100vh. On mobile browsers, 100vh doesn’t always account for the dynamic browser UI (address bar, navigation bar). Using 100dvh instead of 100vh could potentially fix the issue by properly adjusting for the visible viewport height.
GiteaMirror commented 2026-03-22 14:03:28 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 11, 2025):

Will be fixed in https://github.com/go-vikunja/vikunja/pull/1466

@kolaente commented on GitHub (Sep 11, 2025): Will be fixed in https://github.com/go-vikunja/vikunja/pull/1466
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2333
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?