Opened 13 years ago
Closed 13 years ago
#7785 closed defect (worksforme)
ContentPane: destroyRecursive does not filter down all the way
| Reported by: | ben hockey | Owned by: | Sam Foster |
|---|---|---|---|
| Priority: | high | Milestone: | tbd |
| Component: | Dijit | Version: | 1.2beta |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
destroyRecursive does not walk all the way down. as an example, if i had a contentpane that has a toolbar which has buttons, then if i call destroyRecursive on the contentpane, the buttons are not destroyed
Change History (4)
comment:1 follow-up: 2 Changed 13 years ago by
| Owner: | set to Sam Foster |
|---|---|
| Summary: | destroyRecursive does not filter down all the way → ContentPane: destroyRecursive does not filter down all the way |
comment:2 Changed 13 years ago by
Replying to bill:
neonstalwart - You should always attach a test case. In particular with this ticket, there are factors in your test you haven't explained, such as how the content in the ContentPane was loaded (whether in the original HTML, or via an href, or via a attr('content', ...) call etc.,)
i apologize. after creating the ticket, i went on to change my code to get around this and now, of course, after trying for a while, i can't get it back to where it didn't work. i'll try to be more thorough in the future. you should probably close this ticket rather than leave it open.
comment:4 Changed 13 years ago by
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
neonstalwart - You should always attach a test case. In particular with this ticket, there are factors in your test you haven't explained, such as how the content in the ContentPane was loaded (whether in the original HTML, or via an href, or via a attr('content', ...) call etc.,)