Manual input value issue

[Renard]

hi All  

I encountered the following problem while using timepicker.

I have chosen a time when the value in the departure event is correct.

At this point, I manually selected the minute and changed 30 to 00, so the departure time from the event is also correct.

However, when the time is changed to 30 again, the value of the blur event is incorrect and the Change event will not be triggered yet.

Thanks

[Yaswin Vikhaash Rajaretenam]

Hi Renard,

We have validated your query and created a sample based on your requirements. However, we were unable to replicate the issue. Please find the sample and video attached below.

Sample - https://stackblitz.com/edit/angular-7tudwacf-zjhq4nre?file=src%2Fapp.component.html,src%2Fapp.component.ts

In order to gain a better understanding of the scenario you are facing, could you kindly provide the following details:

1. The code in which the TimePicker is rendered.
2. A modified sample in which the issue can be replicated.
3. A video demonstrating the issue.

We appreciate your cooperation and look forward to your response.

Regards,

Yaswin Vikhaash

[Renard]

hi 

I just watched your video and noticed that the first time you selected a date, the ' Chaged ' event was triggered. The first time you manually changed the time to 00, the ' Chaged ' event was also triggered. However, when you manually changed the time to 30 again, only the Blure event was triggered, not the ' Chaged ' event

  

You can also output ev.model.value in the Blur event, and you will find that after manually changing the value for the second time. The input value is inconsistent with the value of the control

Thanks

[Renard]

hi  All      

        Please help to reply to my feedback above,

        thank you

    

[Yaswin Vikhaash Rajaretenam]

Hi Renard,

Based on the validation, we were able to replicate the reported issue "Change event not triggered properly on second time when updating time via keyboard". We have considered this as a bug from our end. We will include the fix in the first week of March 2025. You can track the status of the issue by the below feedback link.

Feedback Link : https://www.syncfusion.com/feedback/65708/change-event-not-triggered-properly-on-second-time-when-updating-time-via-keyboard

Disclaimer: “Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization.”

Regards

Yaswin Vikhaash

[Yaswin Vikhaash Rajaretenam]

Hi Renard,

Query: Change event not triggered properly on second time when updating time via keyboard

Feedback: https://www.syncfusion.com/feedback/65708/change-event-not-triggered-properly-on-second-time-when-updating-time-via-keyboard

We have included the fix for the issue "Change event not triggered properly on second time when updating time via keyboard" with our package version 28.2.11. So, can you please upgrade your package to the latest to resolve the issue from your end?

Release notes: https://ej2.syncfusion.com/angular/documentation/release-notes/28.2.11?type=all#timepicker

Sample: Klqykskm (forked) - StackBlitz

Root cause:

The updateValue method is triggered before the previousValue is updated. This results in the same previousValue being used, which prevents the updateValue method from executing. Consequently, the change event is not fired.

Regards

Yaswin Vikhaash