-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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: The lowest year in the Year navigator dropdown remains disabled when we are applying minDate in date selector #14839
Labels
Type: Bug
Issue contains a bug related to a specific component. Something about the component is not working
Milestone
Comments
mubashshirulislam-nagarro
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 19, 2024
I'm facing the same issue with primeng v16.9.1 and Angular v16.2.12 |
I'm working on this. Thanks, |
akshayaqburst
pushed a commit
to qburst/primeng_qb_4
that referenced
this issue
Feb 21, 2024
…ar navigator dropdown remains disabled when we are applying minDate in date selector
mehmetcetin01140
added
Type: Bug
Issue contains a bug related to a specific component. Something about the component is not working
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 26, 2024
PR for review #14853 |
Same is for max date |
cetincakiroglu
added a commit
that referenced
this issue
Mar 14, 2024
fix: primefaces #14839, Calendar: The lowest year in the Year navigator dropdown remains disabled when we are applying minDate in date selector
Fixed in #14853 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Type: Bug
Issue contains a bug related to a specific component. Something about the component is not working
Describe the bug
Suppose today is 19/02/2024.
And we set the minDate to be 19/02/2021.
Now when we open the calendar and open the year navigator then 2021 seems to be disabled.
Environment
Angular 16.2.0
Primeng 16.5.1
Reproducer
No response
Angular version
16.2.0
PrimeNG version
16.5.1
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.9.0
Browser(s)
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered: