telerik / kendo-angular

Issue tracker - Kendo UI for Angular
http://www.telerik.com/kendo-angular-ui/
Other
468 stars 216 forks source link

[DateTimePicker] Date 1.1.1970 can't be set/delete from input #4432

Open vavrinec-aspecta opened 1 week ago

vavrinec-aspecta commented 1 week ago

Description

When we write the specific value "1/1/1970 1:00 AM" ( time is depend on browser timezone ) in the input, it gets really weird. Sometimes it saves the value but cannot be deleted or it doesn't even save the value.

In general, operations with the date "1/1/1970" are bad.

Potential problem: Apparently, somewhere there is a validation through Date.parse(input) where in the case of the date "1/1/1970" the .parse() method returns the value 0, which is in the condition false. Maybe.

Steps To Reproduce

Many ways of reproduction. This is one of them:

The value has been removed.

Or with setted value we can't delete it:

Test url: https://stackblitz.com/edit/angular-kitaqn-jwajrh?file=src%2Fapp%2Fapp.component.ts

Or the official URL demo: https://www.telerik.com/kendo-angular-ui/components/dateinputs/datetimepicker/events

Screenshots or video

https://github.com/user-attachments/assets/6c167902-f54c-4a39-aafc-8375b3d9ec4b

Actual Behavior

Weird behavior with "1/1/1970 1:00 AM" ( time is depend on browser timezone ) value.

Expected Behavior

Normal behavior like any other values

Browser

Chrome, Microsoft Edge

Browser version

latest

OS type

Windows

OS version

Win 11

Last working version of the Kendo UI for Angular package (if regression).

No response

zstoyanova9 commented 3 days ago

Hi @vavrinec-aspecta, thank you for the detailed explanation.

I tried to reproduce the described issue on my side, but it seems that I can enter the mentioned date ("1/1/1970 1:00 AM") in the DateTimePicker as expected. Please check the following screen recording for reference:

https://github.com/user-attachments/assets/3ed53cdc-72b1-4fa5-93f6-2dc27aa10e25

Having said that, could you please clarify the exact timezone, in which the reported issue is experienced on your side? The timezone on my side is Eastern European Summer Time (EEST), with a UTC offset of -180 minutes (UTC+3).

Thank you in advance.