Trigger becameInactive event when active spy destroyed.#152
Merged
Conversation
Owner
|
Looks great, thanks! |
oblador
added a commit
that referenced
this pull request
Oct 13, 2015
Trigger becameInactive event when active spy destroyed.
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.
When a spied-upon element is destroyed, and that spy is currently active, trigger the
duScrollspy:becameInactiveevent. This doesn't matter if the client code is just using the class for styling, but if it's actually making use of thebecameActive/becameInactiveevents then the client will end up in the wrong state. This also maintains symmetry withaddSpy, which forces the handler to run (and possibly triggerbecameActive) as soon as the spy is added.