fixes calendar bug #91
Merged
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
|
I think I remember that browsers can interpret Could you have a look at this and if it is workable, please update the test. |
|
@zemogle updated the test, changes look great! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
QUICK FIX: Calendar bug
Background:
Edward pointed out that the calendar rendered January 1970 on his end as the initial page. This was probably due to setting the
max-dateasnew Date(currentSemesterEnd)rather than just havingcurrentSemesterEndwhich already is a dateOn my end, after further inspection, I noticed that it would sometimes block out the initial page (November 2024)
