fix(AUT-2298): Bug fix for years that default incorrectly #568
Merged
lizzielerwill-ctrl merged 3 commits intomainfrom Jan 20, 2026
Merged
fix(AUT-2298): Bug fix for years that default incorrectly #568lizzielerwill-ctrl merged 3 commits intomainfrom
lizzielerwill-ctrl merged 3 commits intomainfrom
Conversation
commit: |
AlanFnz
approved these changes
Jan 20, 2026
lizzielerwill-ctrl
deleted the
feat/AUT-2298-datepicker-range-input-fix
branch
github-actions bot
pushed a commit
that referenced
this pull request
Jan 23, 2026
## <small>2.49.1 (2026-01-23)</small> * fix(AUT-2298): Bug fix for years that default incorrectly (#568) ([5568a13](5568a13)), closes [#568](#568) * fix(ci): extend GITHUB_TOKEN permissions for release (#571) ([85a6fc6](85a6fc6)), closes [#571](#571) * fix(ci): publishing doesn't work (#570) ([6b5dcd7](6b5dcd7)), closes [#570](#570)
Contributor
|
🎉 This PR is included in version 2.49.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What
Ticket Link here
It was noticed in the Dispatcher project that there can be some odd behaviour when a user uses backspace to delete numbers from the year in the date picker.
If a user has 12/12/2025 inputted in the datepicker and they then try to delete 3 numbers, the year defaults to 1920 and the user gets "stuck" unable to correct the year. This is because of JavaScript's legacy date parsing. The new Date() constructor treats years between 0 and 99 as always beginning with 19 (e.g., new Date(24, 0, 1) becomes January 1, 1924).
This PR adds
setFullYear()to thecalendarDateToDatefunction. This function correctly sets the year to the number provided, so 25 is treated as 25, not defaulted to 1925.Media
Before:
Screen.Recording.2025-12-01.at.11.02.07.1.mov
After:
Screen.Recording.2026-01-20.at.00.09.26.mov