This repository has been archived by the owner on Dec 15, 2017. It is now read-only.
1970-01-01 00:00:00 can't be entered manually #154
Conversation
This file contains 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
Fix bug that causes the input to get removed when date/time entered equals "1970-01-01 00:00:00 UTC" (beginning of unix epoch)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
If you enter the date 1970-01-01 and time 00:00:00 into the input field and then move the focus away from the input field the field gets emptied. This only happens when you type that date and time, not when you use the datetimepicker itself.
The bug is caused by function setValue(newDate) when the parameter newDate equals 0 (the integer representation of aforementioned date).