Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nzFormat in DatePicker doesn't parse manual value in input #5188

Closed
nitrexx opened this issue Apr 30, 2020 · 5 comments
Closed

nzFormat in DatePicker doesn't parse manual value in input #5188

nitrexx opened this issue Apr 30, 2020 · 5 comments

Comments

@nitrexx
Copy link

nitrexx commented Apr 30, 2020

Reproduction link

https://stackblitz.com/edit/angular-qetubt

Steps to reproduce

Set custom nzFormat to "dd.MM.yyyy" and try to manually fill up to the DatePicker input.

What is expected?

Parse this date after press Enter a set value to the DatePicker .

What is actually happening?

Nothing, no parse, no event, exactly nothing.

Environment Info
ng-zorro-antd 8.5.2
Browser Chrome Version 81.0.4044.122 (Official Build) (64-bit)

The same problems from 2018:

@daxilshah
Copy link

@nitrexx Did you check this? #5094

@nitrexx
Copy link
Author

nitrexx commented May 1, 2020

Yes, I did, but it still doesn't work.

https://stackblitz.com/edit/angular-qetubt-6cskmr

@wenqi73
Copy link
Member

wenqi73 commented May 1, 2020

@nitrexx 9.0.0 has supported this, plz update.

@wenqi73 wenqi73 closed this as completed May 1, 2020
@sainisagar310
Copy link

sainisagar310 commented May 10, 2020

Still, there is an issue with typing date manually into a date-picker. When the date-picker is getting focused, the calendar would open, and then it works fine whether you type a date or select one from the picker. But when you re-click the input so the picker gets away and then when you type a date in but it won't be changed.

I also recorded a video on the following link that can help to reproduce the issue.
https://1drv.ms/v/s!AsAm4FCl_e_nmgQx3Evxa1O1AZ8z

This is something you should fix it and release into the coming versions as per your comfort. But currently I'm also looking for a quick solution if possible.

@wenqi73
Copy link
Member

wenqi73 commented May 14, 2020

@sainisagar310 Thanks for reporting this, please track #5284.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants