Click on button a couple of times quickly and you will see problem. For DateTimePicker:
Also, the similar problem for DatePicker:
SPSureshkumar P Syncfusion Team January 30, 2020 08:06 AM
While analyzing the reported issue with the provided sample, the issue is occurred due to delay in the component rendering while clicking the button quickly. So, the element does not get at that time. So, can you please share the details that if possible, to disable the button on the second time click rather than the quick click of the button in your application else destroy the component by using our public destroy method in the button click that details help us to check and proceed at our end.
This issue occurs with form binding librairies too.
When another input is being filled, the form will be reevaluated and the component re-rendered leading to the syncfusion component to crash eventually when the user types in too quickly.
Can you provide a fix date and/or a target release for that issue ?
ps: I have the issue with DateRangePicker
BCBerly Christopher Syncfusion Team February 13, 2020 10:17 AM
Thank you for contacting us.
We could not replicate the reported issue based on the provided information. Kindly share the below details to help us check this issue at our end.
Sufficient code to replicate the issue
Issue reproducible sample (If possible)
Please explain the details of the issue “When another input is being filled, the form will be reevaluated and the component re-rendered leading to the Syncfusion component to crash eventually when the user types in too quickly”.
Also confirm whether you have faced same kind of issue like “cannot read property id of undefined”.
The above information will help us provide a prompt solution.
PDPavel DanilchykFebruary 25, 2020 04:36 AM
Hello again. This video illustrates how bugs can be reproduced for DateTimePicker / DatePicker components.
BCBerly Christopher Syncfusion Team February 26, 2020 07:05 AM
Thanks for providing information.
We have already replicated the reported issue and provided our justification details to you in our second update dated on January 30th, 2020.
We requested details to replicate the issue to another customer Nicholas as the issue reported by him is different from yours.
NBNicolas BeaumerFebruary 27, 2020 08:07 AM
Pavel's information are quite clear on the bug. So I am confident this is the same issue (the id of undefined one).
Please provide a fix date/release target for that issue. If that doesn't solve my problem, I'll find a way to get you the details you need to investigate my problem in particular.
I am using the same library version number as Pavel.
Thanks for your help!
BCBerly Christopher Syncfusion Team February 28, 2020 07:47 AM
Deeply regret for the inconvenience caused.
As we mentioned earlier, the reported issue caused due to click the button rapidly. We could not predict this case in our source and provide the fix at our end. So, we suggest you to enable the button in the destroy event to get rid of the issue at your end.