It appears that the helper text here “leave blank to use the time of form submission” is untrue. Once I entered a time, the form accepted the submission.
So I think that I am understanding that in order for the date and time autofill to work, both need to be left blank. You cannot enter the date and then expect the time to autofill with today or vice versa. Is that intended behavior here?
I think that’s correct and I agree it can be confusing. My understanding is that they both need to be specified or both need to be blank.
I don’t think it makes sense to enter a date and then autofill the current time.
The other way around potentially does make sense though - where you enter a time and it autofills the date with today’s date.
More broadly, I think there’s a functionality gap in terms of not having a way to generically specify a date without specifying a time. It has been discussed whether having the birthdate be a timestamp is actually the best thing.
Perhaps it would be better to have “birthdate” be a date field and - if necessary - have a separate “time of birth” field for those who need to track when in the day a birth actually happened…
I think so. Data-model questions aside, the immediate bug (IMHO) is that the error message should be clearer for this case.
@Symbioquine Thank you for these thoughts.
I agree, a better error message would be nice.
I will say that time of day is not a relevant field to me. Separating it out from date and making it an optional fill would be my ideal. But all in all, not a big deal either way.
Here is the existing bug report: Date format error on test logs. · Issue #625 · farmOS/farmOS · GitHub
And a related pull request (this does not fix the issue, but aims to improve UX generally): Hide datetime time field element by default by mstenta · Pull Request #637 · farmOS/farmOS · GitHub