igx-timepicker In dropdown mode if we click cancel button without selecting any value null values are displaying

[sjPrajwal]

Description

In Dropdown mode if we click cancel button without selecting any value null values are displaying and after that can't select any time.

• igniteui-angular version: 4.3.3
• browser: Chrome

Steps to reproduce

Active dropdown mode and give min and max values

1. open the timepicker in dropdown mode
2. click on cancel button and notice the input field value, null will display
3. again clear field and try to select the time again still it will display null.

Result

on cancel, time picker taking null values

Expected result

on cancel, time picker shouldn't take any values.

Attachments

Attach a sample if available, and screenshots, if applicable.

[Lipata]

Hi, @sjPrajwal.

I'm trying to reproduce your problem and I'm using the following demo. When I follow your steps I see an error, but in the input I see the following value: NaN:NaN AM. Please tell me if this is what you see, or if the problem is different, please modify the demo that I'm sending you. Thank you in advance!

[sjPrajwal]

Hi team, Yes, issue is same as produced by you, please fix it asap. Regards, Prajwal.

…

On Mon, 20 Jan 2020, 6:11 pm Nikolay Alipiev, ***@***.***> wrote: Hi, @sjPrajwal <https://github.com/sjPrajwal>. I'm trying to reproduce your problem and I'm using the following demo <https://stackblitz.com/edit/time-picker-mix-max?file=src/app/timepicker-sample-8/timepicker-sample-8.component.html>. When I follow your steps I see an error, but in the input I see the following value: NaN:NaN AM. Please tell me if this is what you see, or if the problem is different, please modify the demo that I'm sending you. Thank you in advance! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6494?email_source=notifications&email_token=AICLLK4D3MY6NC7G73HKZ53Q6WLWJA5CNFSM4KJAUZZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJMPYLI#issuecomment-576257069>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AICLLK3BPXQI52ETNKXMA63Q6WLWJANCNFSM4KJAUZZA> .

[sjPrajwal]

Hi @Lipata @jackofdiamond5 ,
any updates on the issue..?

[jackofdiamond5]

Hi @sjPrajwal,

Please excuse our delayed response. We have moved this issue to our next sprint where we will take a closer look at how we may fix it. In the meantime, we remain open for any additional questions or comments you might have.

[sjPrajwal]

Hi @jackofdiamond5 ,
Any updates on the issue reported...?
I am looking status resolved..

[Lipata]

Hi, @sjPrajwal. We are currently making code review and verifying the issue. Expect that this will be part of our 8.2.19 and 8.1.24 releases, next Monday.

[sjPrajwal]

Hi Nikolay, Thank you very much for your reply. I found one more issue. can i ask here only. Regards, Prajwal.

[Lipata]

Hi, @sjPrajwal.

If it is #6585, we are checking it and we will write in the corresponding issue. If the issue you are experiencing is another one and is not also related to the current one, we prefer a new issue with demo (e.g. in StackBlitz). Thank you, @sjPrajwal.

[sjPrajwal]

Hi Nikolay, i am asking #6585 <#6585> issue only, waiting for your reply. Thanks a lot.

…

On Wed, Feb 5, 2020 at 1:39 PM Nikolay Alipiev ***@***.***> wrote: Hi, @sjPrajwal <https://github.com/sjPrajwal>. If it is #6585 <#6585>, we are checking it and we will write in the corresponding issue. If the issue you are experiencing is another one and is not also related to the current one, we prefer a new issue with demo (e.g. in StackBlitz). Thank you, @sjPrajwal <https://github.com/sjPrajwal>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6494?email_source=notifications&email_token=AICLLK4WCPN423SKLGMPFKLRBJX3VA5CNFSM4KJAUZZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK2QNRY#issuecomment-582289095>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AICLLK4GX6ICU5FDWIUH74DRBJX3VANCNFSM4KJAUZZA> .

[sjPrajwal]

Hi @Lipata ,
Any updates regarding this bug??

[Lipata]

Hi, @sjPrajwal.

We've currently released 8.2.19 and 8.1.24, the packages that I have mentioned. However, because of the official Angular 9 release last week, we needed to hold some of our PR and first release our Angular 9 compatible version. In addition to that our 8.2.x and 8.1.x and 9.0.x should be synchronized and currently, the fix is not still merged. Please expect the fix in the next versions and thank you for the patience!

[Lipata]

@sjPrajwal you can use [email protected] or [email protected]