Closed GeOdin closed 1 year ago
@Patrick-Nijman
Hey Patrick :)
I gave this ticket priority 2 because it currently only is on staging. But it is something a lot of people will notice without workaround (I think).
I did the same for https://github.com/nens/servicedesk-issue-only/issues/135
Kind regards
Another note: clicking on a date in the datetime picker always causes the input field (in the rain tool, outside the datetimepicker) to show Invalid date (also for all options).
Note this happens when selecting any date in the datetime picker.
For example, when not changing the date, you can create a radar rain.
The rain is applied.
But when you select any date, even if it is just the same date (the date of yesterday in this example), you get NaN and undefined for dates and time. I only clicked on the date in the date input field and then clicked on 29 in the example below.
Opgelost voor de release van 6 feb.
Contact Details
No response
Topdesk URL (API)
No response
Incident Type
Error
What priority should we assign to this submission?
Prio2 Urgent
3Di component
Livesite
What happened?
I could not pick a date with the datetime picker (for a radar/ forecast rain).
How to Reproduce?
Open a browser (happens on Chrome/ Firefox and Edge) Select and start a model (for example v2_bergermeer_with_grndwtr #111 and template with_grndwtr Select rain in the left toolbar Select radar or forecast Try to select another date/time (I tried to look for 28 July 2014 via selecting on the year and then the year range, but I think selecting any date and/ or time causes the issue). You get undefined and NaN as date and time (and Invalid date in input field)
If you press undefined NaN in the datetime dialog, it crashes
What did you expect and what was the actual result?
I expected that I could use the date time picker to pick a date
Add screenshots, video's etc
Click on a date
Option 1 from here
You get invalid date Go back to not crash (click outside dialog)
Option 2
You get invalid date. Click on invalid date to get 4rd screenshot.
Clicked on invalid date
Go back to not crash (click outside dialog)
Option 3 crash
Click on undefined NaN in dialog (top)
Crash
Relevant log output
Additional info
Note: does not happen on production (Chrome) (yet). So it probably has something to do with recent changes in staging.
Did the date time for Lizard recently changed (and is it not yet adjusted to work with the datetime picker)? Is a new version used for the datetime picker on staging?
Another note: just changing the time does work!
Good luck! :)