You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When entering a date with the dateFormat “dd.mm.y”, the century 1900 is used once and 2000 the other time. Entering “31.12.34” results in 31.12.2034 and entering “01.01.35” results in 01.01.1935. We only want dates in the range 01.01.00 - 31.12.99 which should result in 01.01.2000 - 31.12.2099. Have I missed something and this should be configured with parameters?
So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you open a new issue so we can include it in our roadmap?
Thanks a lot for your understanding!
Best Regards,
Describe the bug
When entering a date with the dateFormat “dd.mm.y”, the century 1900 is used once and 2000 the other time. Entering “31.12.34” results in 31.12.2034 and entering “01.01.35” results in 01.01.1935. We only want dates in the range 01.01.00 - 31.12.99 which should result in 01.01.2000 - 31.12.2099. Have I missed something and this should be configured with parameters?
Environment
Latest 17-PrimeNG and Angular 17 version.
Reproducer
https://stackblitz.com/edit/mggu44-ksc5ad
Angular version
17.x.x
PrimeNG version
17.x.x
Build / Runtime
Angular CLI App
Language
ALL
Node version (for AoT issues node --version)
20.10
Browser(s)
No response
Steps to reproduce the behavior
Expected behavior
The text was updated successfully, but these errors were encountered: