Fix DateRangePicker3 bug when initialMonth is equal to the maxDate's month #6548
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #6546
The bug occurs when
initialMonthAndYear
is equal to themaxDate
's month and year resulting in a buggy selection state.We already handle this special case when using
props.initialMonth
orvalue[0]
as the initial month, this PR just expands the special case check to also include thetoday
anddateBetween
cases.Checklist
Changes proposed in this pull request:
Additionally checks that
today
ordateBetween
(if being used as initialMonth) is not the same month asmaxDate
s month and if it is use the previous monthReviewers should focus on:
Screenshot
Testing locally on the docs app setting the minDate as and
new Date(2023, 9, 23)
and maxDate asnew Date(2023, 10, 15)
before:
after: