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: showMinMaxRange - cannot access the month that contains the minDate #4520

Closed
rowlandwilliams opened this issue Jun 16, 2023 · 3 comments
Assignees
Labels
Resolution: Duplicate Issue has already been reported or a pull request related to same issue has already been submitted
Milestone

Comments

@rowlandwilliams
Copy link

rowlandwilliams commented Jun 16, 2023

Describe the bug

When setting showMinMaxRange property on the calendar component, the month that contains the minDate cannot be accessed as the previous arrow button is disabled in the month after.

For example if your minDate was "2023-04-16" (16th April 2023), the previous arrow is disabled in May 2023 so April cannot be accessed. The previous arrow should be disabled when in April 2023 and active in May 2023 to enable access.

Reproducer

https://stackblitz.com/edit/react-hwawjd-hdzdd5?file=src%2FApp.js

PrimeReact version

9.5.0

React version

18.x

Language

TypeScript

Build / Runtime

Next.js

Browser(s)

No response

Steps to reproduce the behavior

  • Open the reproducer
  • Try navigate back to the April and view the minDate (16th).
  • You will not be able to and the furthest back you can view is 1st May

Expected behavior

Expect the month which contains the minDate to be accessible and the previous button to not be disabled in the month after

@rowlandwilliams rowlandwilliams added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jun 16, 2023
@melloware
Copy link
Member

I think its fixed in upcoming 9.6.0 with this: #4456

@melloware melloware 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 Jun 16, 2023
@melloware melloware added this to the 9.6.0 milestone Jun 16, 2023
@melloware melloware self-assigned this Jun 16, 2023
@melloware
Copy link
Member

OK I just tested your scenario and can confirm its fixed in 9.6.0

@melloware melloware closed this as not planned Won't fix, can't repro, duplicate, stale Jun 16, 2023
@rowlandwilliams
Copy link
Author

Great thanks @melloware

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

2 participants