Improved jQuery.timers initialization on partial page updates #2
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
put plugin into document-ready call to improve integration with multiple jQuery instances (for example, when parts of the page are loaded via jQuery.load and their html includes jQuery.timers).
Bump version to 1.2.1
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.
Hi there,
Problem:
jQuery.timers initialization, when performed from partial page updates (for example, when parts of the page are loaded via jQuery.load), fails with various error messages (like "jQuery.timer not found").
Solution:
The problem is gone, as soon as we put jQuery.timers initialization into document-ready call. The suggested change in the source code is doing exactly this.
Additionally I added README.md and CHANGES.md.