Actions
Bug #14303
closeddatetime broken with picker
Start date:
10.06.2022
Due date:
% Done:
0%
Estimated time:
Discuss:
Prio Planung:
No
Vote:
Description
We do have a lot of SQL date and datetime fields in our database, the corresponding forms use date and datetime form-elements.
Extension config: config.dateFormat = yyyy-mm-dd, so all input is YYYY-MM-DD and YYYY-MM-DD HH:mm respectively
When adding the relevant CSS and JS files, these fields are all broken.
Without manual intervention:- the fields only show datepicker even for datetime fields
- existing dates and newly selected dates end up like
2022-37-Fr
(when selecting 2022-06-10 or if the record in the DB contains that date)
dateFormat = YYYY-MM-DD HH:mm
datetimeSideBySide = true
to FormElement.parameter
of a datetime field:
- date and time picker are shown correctly
- datetime picked is displayed correctly
- datetime is stored correctly
- stored values from the record are not shown anymore, instead the filed is displayed as if empty
- stored values should be loaded correctly
- the default dateFormat should respect the global config (an not require a manual intervention on every single date or datetime field.)
- datetimeSideBySide should be true for datetime fields
Further minor wish: When the first field in a form is a date or datetime field, the picker is only opened after it looses and regains focus. It would be nice if the picker was opened on load directly. (but this is probably a Browser-Javascript problem.)
Related issues
Actions