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

p-calendar #14309

Closed
jaggi510 opened this issue Dec 8, 2023 · 2 comments
Closed

p-calendar #14309

jaggi510 opened this issue Dec 8, 2023 · 2 comments
Labels
Resolution: Duplicate Issue has already been reported or a pull request related to same issue has already been submitted

Comments

@jaggi510
Copy link

jaggi510 commented Dec 8, 2023

Describe the bug

Issue with year picker.
When you have min date and max date on the p-calendar within a year. It is not allowing to select 2023 and 2024. It is only allowing 2024. Year 2023 is disabled. Once we pick a date in 2024 and then try to change back to a date in 2023, Only way to do this is by clicking on month navigator as year 2023 is disabled on year selection.

Environment

angular 16.2.11, with primeng 16.6.0

Reproducer

https://stackblitz.com/edit/github-mz6vwk?file=src%2Fapp%2Fapp.component.html

Angular version

16.2.11

PrimeNG version

16.6.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

v20.2.0

Browser(s)

Version 120.0.6099.71

Steps to reproduce the behavior

set min date as today
max date as today + 1 year

on p-calendar set minDate and maxDate.

Expected behavior

We should be able to select year 2023 and 2024. But only 2024 is selectable. If you select any date in 2024, and then click on year, We should be able to see both 2023 and 2024 as selectable.

@jaggi510 jaggi510 added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Dec 8, 2023
@Draganlazarev90
Copy link

Still present in 17.4

@cetincakiroglu cetincakiroglu added this to the 17.12.0 milestone Mar 14, 2024
@cetincakiroglu
Copy link
Contributor

Hi,

Thanks a lot for reporting the issue. This issue is duplicate of #13919
Related issue is fixed and the fix will be available with upcoming release (17.12.0).

Closing this one.

@cetincakiroglu cetincakiroglu added Resolution: Duplicate Issue has already been reported or a pull request related to same issue has already been submitted and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Mar 20, 2024
@cetincakiroglu cetincakiroglu removed this from the 17.12.0 milestone Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Duplicate Issue has already been reported or a pull request related to same issue has already been submitted
Projects
None yet
Development

No branches or pull requests

3 participants