Opened 13 years ago
Closed 10 years ago
#4579 closed defect (wontfix)
ContentPane: IE6 is unable to truely remove form nodes, this causes a pseudo memory leak in the content pane widget
| Reported by: | guest | Owned by: | |
|---|---|---|---|
| Priority: | high | Milestone: | 1.5 |
| Component: | Dijit | Version: | 0.9 |
| Keywords: | Cc: | [email protected]… | |
| Blocked By: | Blocking: |
Description (last modified by )
See this post regarding the issue, with links to test cases. This post has a proposed solution, there is a practical dojo example and a fix file.
Some thought needs to be given to the formManager function and how it could be integrated into the toolkit.
Although the content pane widget is the most obvious practical example of the bug, it would be highly valuable if the toolkit had the system in place to manage form nodes in IE6 OOTB. Part of my research found that (as best I could see) on Dojo seemed to offer any destroyNode type of feature.
Attachments (1)
Change History (4)
Changed 13 years ago by
comment:1 Changed 12 years ago by
| Component: | General → Dijit |
|---|---|
| Milestone: | 1.1 → 1.4 |
| Owner: | anonymous deleted |
| Summary: | IE6 is unable to truely remove form nodes, this causes a pseudo memory leak in the content pane widget → ContentPane: IE6 is unable to truely remove form nodes, this causes a pseudo memory leak in the content pane widget |
comment:2 Changed 11 years ago by
| Milestone: | 1.4 → 1.5 |
|---|
bumping 1.4 tickets to 1.5, and most 1.3 tickets to 1.4
comment:3 Changed 10 years ago by
| Description: | modified (diff) |
|---|---|
| Resolution: | → wontfix |
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
the fix file I used in the test case using the content panel