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

Calendar: Actual value is not being limited by yearRange when manually typing #7691

Closed
Minitron5000 opened this issue Feb 11, 2025 · 0 comments · Fixed by #7701
Closed

Calendar: Actual value is not being limited by yearRange when manually typing #7691

Minitron5000 opened this issue Feb 11, 2025 · 0 comments · Fixed by #7701
Labels
Type: Bug Issue contains a defect related to a specific component.
Milestone

Comments

@Minitron5000
Copy link

Describe the bug

Actual value is not being limited by yearRange when manually typing

Reproducer

https://stackblitz.com/edit/hr4nfxsy

System Information

System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    primereact: latest => 10.9.2 
    react: 18.3.1 => 18.3.1

Steps to reproduce the behavior

  1. Manually type in calendar a date that exceeds the range ( for example 01/01/2000 )
  2. Click outside of the input

Result: Displayed date in the input switches to match the limit ( 01/01/2020 ). But the actual value that that was received from the input in onChange handler is the invalid one which was typed in ( 01/01/2000 ).

Expected behavior

Expected: Displayed date in the input switches to match the limit ( 01/01/2020 ). The actual value that that was received from the input in onChange handler should be the same ( 01/01/2020 )

@Minitron5000 Minitron5000 added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Feb 11, 2025
@melloware melloware added Type: Bug Issue contains a defect related to a specific component. and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Feb 12, 2025
@melloware melloware added this to the 10.9.3 milestone Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a defect related to a specific component.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants