fix(datetime): switching months in wheel picker now selected nearest neighbor #25559
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.
Pull request checklist
Please check if your PR fulfills the following requirements:
ionic-docs
repo, in a separate PR. See the contributing guide for details.npm run build
) was run locally and any changes were pushednpm run lint
) has passed locally and any fixes were made for failuresPull request type
Please check the type of change your PR introduces:
What is the current behavior?
Issue URL: Internal ticket.
In #25422 (comment) it was discovered that switching months in the new
preferWheel
date picker would sometimes reset the selected day to 1.This was happening when switching between months with different maximum days. For example, selecting May 31st then switching the month to April would cause the 1st to be selected. This is because there is no April 31st.
Under the hood, we were filtering the 31st out of the items passed into the picker column, and the picker column did not know what to do.
What is the new behavior?
items
prop changes, the picker column will check to see if the selected item is still in theitems
array.items
array. If the index is not found, it returns early.items
, starting at the last known position of the selected item.value
prop is updated and the nearest item is selected.feature-6.2
before.mov
after.mov
Does this introduce a breaking change?
Other information