Search and Top Navigation
#6898 closed bug (invalid)
Opened January 25, 2011 03:18PM UTC
Closed November 12, 2012 09:10AM UTC
Calling destroy on draggables causes orphans in IE8
| Reported by: | aws | Owned by: | aws |
|---|---|---|---|
| Priority: | minor | Milestone: | 2.0.0 |
| Component: | ui.draggable | Version: | 1.8.9 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Test page: http://jsbin.com/upagi4/2/
I've linked to a pretty bare minimum example. The example turns two spans into draggables then calls destroy and remove on them.
If you open the test page with sIEve in IE8, when you click 'Run tests' followed by 'Remove tests' and open 'Show-in-use' in sIEve, you will see that the two spans that were turned into draggables then destroyed/removed are now 'orphans'. Orphans seem to essentially be a leak, as no matter how long sIEve is left open, they never seem to be reclaimed.
Attachments (0)
Change History (4)
Changed January 25, 2011 03:19PM UTC by comment:1
Changed October 11, 2012 02:49PM UTC by comment:2
| milestone: | 1.9.0 → 2.0.0 |
|---|
Changed October 28, 2012 07:59PM UTC by comment:3
| owner: | → aws |
|---|---|
| status: | new → pending |
Thanks for taking the time to contribute to the jQuery UI project! I can no longer reproduce the issue using the latest jQuery and jQuery UI. http://jsbin.com/upagi4/4/edit
If you can still reproduce it, please feel free to reply to this ticket with a test case showing the problem. Thanks!
Changed November 12, 2012 09:10AM UTC by comment:4
| resolution: | → invalid |
|---|---|
| status: | pending → closed |
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!
I should have clarified that the test page is using jQuery 1.4.4 and jQuery UI 1.8.9, but that the problem also occurs with jQuery 1.4.3 and jQuery UI 1.8.0.