This repository was archived by the owner on Mar 8, 2019. It is now read-only.
Update calls to stop(), which now takes an increment, not a timeout value #1
Conversation
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
…alue If we really want a timeout, we can set one globally via QUnit.confg.testTimeount. See qunitjs/qunit#125 for background.
tiff
added a commit
that referenced
this pull request
Nov 1, 2011
Update calls to stop(), which now takes an increment, not a timeout value
|
Thanks very much! |
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.
Update calls to stop(), which now takes an increment, not a timeout value
If we really want a timeout, we can set one globally via QUnit.confg.testTimeount.
See qunitjs/qunit#125 for background.