[FIX] Manual date input fails on YYYY

[fatmarker]

Describe the bug:

When manually entering date values in Organized, tabbing to or clicking on the empty year field causes the date entry to disappear.

Steps to reproduce the issue:

Tested on macOS Safari using different date formats. The following steps assume DD.MM.YYYY, but the same issues occur for MM/DD/YYYY.

Part 1

1. edit a person record
2. add a new Time away entry
3. note: the start date is autofilled, including the year (see part 2 below)
4. click on the end date DD and begin entering a valid value
5. tab or click to MM and do the same
6. tab or click to YYYY and the entire entry disappears

The same issue occurs when manually entering the date of the CO visit.

Part 2
Although the start date is pre-populated with the current date, manually editing the year clears the MM and DD values.

Expected behavior:

Manually input dates without the need for the widget.

Additional: Expected UX behavior

• currently, the calendar widget steals focus from the input field; retaining focus while opening the widget should be possible
• the calendar widget requires clicking an arrow for the next month, but months with 5 rows have a larger height, making the next button jump up on some months, interrupting clicks. The calendar should account for a max-height scenario to keep interactive elements from shifting
• when a start date is set, it should not be possible to choose, set or save an end date that is less than the start date
• when using the widget to set an end date, it should open up on the month of the start date and not the current month

Screenshots

Organized.manual.date.input.bug.mp4

Which platform can you reproduce the bug on?

Desktop

Your operating system:

macOS

App version:

v3.37.1

Additional information

This bug is not new, I'm just getting around to reporting it now. It has existed since at least v3.35

[ux-git]

Thanks for the great points @fatmarker We will take a look what we can implement.

The date-entry behavior can indeed feel a bit weird at first. It’s currently handled by one of our code dependencies as I believe, which we can’t modify very easily. Once again, thank you for reporting it, we’ll see how far we can improve it within those limits.