#7165 closed bug (fixed)
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 (9)
Changed 13 years ago by
comment:2 Changed 13 years ago by
| Component: | unfiled → manipulation |
|---|---|
| Milestone: | 1.4.2 → 1.4.5 |
| Priority: | undecided → blocker |
comment:5 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | open → closed |
Fix #7717 and #7165. Thanks to dmethvin and iliakan for their help fixing these issues.
Changeset: faefbb1ad0b81e8001b582d06d5bd9c9236e62ce
comment:6 Changed 13 years ago by
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
comment:7 Changed 13 years ago by
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
comment:8 Changed 13 years ago by
| Milestone: | 1.4.5 → 1.5 |
|---|
Move fixed tickets to appropriate milestone
test case showing the leak