Replaces use of jQuery object as container with native Array - #5
Open
anddoutoi wants to merge 1 commit into
Open
Replaces use of jQuery object as container with native Array#5anddoutoi wants to merge 1 commit into
anddoutoi wants to merge 1 commit into
Conversation
…ative Array. The methods .add() and .not() creates a new jQuery object that keeps a reference to the old jQuery object in its property .prevObject.
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
1 participant
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.
A jQuery object keeps a reference to the "replaced" jQuery object in .prevObject when using .add() and .not(). This could result in a leek of memory cause detached and removed DOM elements will still be referenced.