Fixed bug with events displaying on the wrong month when clicking the next or previous month buttons rapidly#48
Open
pmachapman wants to merge 1 commit into
Open
Conversation
|
+1 I have the same problem and i have done the same fix. |
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.
If Monthly.js is set up to load its events from a URL, and the user rapidly clicks the next or previous month buttons, then the events from multiple months will sometimes display all together on one month. This is especially noticeable if the server is slow at generating the XML/JSON, or if the user has a slow connection.
This change fixes the bug by only adding events that are for the current month and year.