"Please provide a title for the filter" warning given when title already filled out, prevents saving #2084
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#2084
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Description
When editing a project filter you get the warning "Please provide a title for the filter" even when the title is already filled out and it prevents you from saving unless put focus in the title field and move focus away from the title field again. You don't actually have to change the title.
Vikunja Frontend Version
0.22.0
Vikunja API Version
0.22.0
Browser and version
Edge 120.0.2210.77 & Chrome 120.0.6099.129
Can you reproduce the bug on the Vikunja demo site?
Yes
Screenshots
Thank you for the report.
How did you open the title field without having the input focused right away? I was not able to reproduce this using the following steps:
As expected, the filter is saved and the popup closes.
I just tried it in the demo site.
The cursor focus should be in the title field and show the red message in the screenshot from the original issues report. Click Description or anywhere else and it remains.
Same thing happens if I click the ... > Edit in the left menu
Still wasn't able to reproduce. Can you share a screen recording?
See attached video. Near the end I ended up putting a space in the title before navigating away and saving successfully but you don't need to. You only need to tab out of the field. Clicking focus away from it, like clicking into description, does not get rid of the error for me. The recorded example was in Safari on macOS but the same thing happened in Chrome in Edge on windows as per the original report.
Still wasn't able to reproduce it consistently, but managed to see the behaviour you're describing once in a Windows 10 vm with Edge. I've pushed a potential fix in
e3cae0ed7f
- please check with the next unstable build (ready in ~45 min) if the problem still happens.This was reported as fixed via email, closing. Please ping again if you still have issues.