Side navigation
#7165 closed bug (fixed)
Opened October 12, 2010 05:38PM UTC
Closed December 23, 2010 12:21AM UTC
Last modified December 24, 2010 12:05PM UTC
wrap leaks objects in $.cache
Reported by: | IgorMinar | Owned by: | |
---|---|---|---|
Priority: | blocker | Milestone: | 1.5 |
Component: | manipulation | Version: | 1.4.2 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
If a node is created via wrap, it is not properly removed from the cache when it's no longer part of the DOM.
See attached test case.
Attachments (1)
Change History (8)
Changed October 14, 2010 05:17AM UTC by comment:1
status: | new → open |
---|
Changed October 23, 2010 11:05PM UTC by comment:2
component: | unfiled → manipulation |
---|---|
milestone: | 1.4.2 → 1.4.5 |
priority: | undecided → blocker |
Changed December 18, 2010 07:29PM UTC by comment:3
Changed December 19, 2010 12:04AM UTC by comment:4
Fixed the pull: https://github.com/jquery/jquery/pull/137
Changed December 23, 2010 12:21AM UTC by comment:5
Changed December 23, 2010 12:21AM UTC by comment:6
Update cloneCopyEvent so that it does not create superfluous data objects when cloning elements. Exposes a new method, $.hasData. Fixes #7165. Thanks to DaveMethvin and iliakan for their help.
Changeset: f28c774f2cde004a33aefc28306d995c599d963b
Changed December 24, 2010 12:05PM UTC by comment:7
Update cloneCopyEvent so that it does not create superfluous data objects when cloning elements. Exposes a new method, $.hasData. Fixes #7165. Thanks to DaveMethvin and iliakan for their help.
Changeset: f28c774f2cde004a33aefc28306d995c599d963b
Changed January 14, 2011 10:20PM UTC by comment:8
milestone: | 1.4.5 → 1.5 |
---|
Move fixed tickets to appropriate milestone
live test case