Changes between Initial Version and Version 5 of Ticket #7959
- Timestamp:
- Nov 5, 2008, 1:31:32 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #7959
- Property Owner set to Sam Foster
-
Property
Status
changed from
new
toclosed
-
Property
Resolution
changed from
to
duplicate
-
Ticket #7959 – Description
initial v5 1 1 In my code, I am creating a tree and when something changes in a critical section of my application, I am removing the old tree and adding a new one. The tree is attached to a ContentPane or an ExpandoPane. Well the ContenPane.destroyDescendants() function in 1.2-0b1 was a direct call to it's parent - dijit._Widget.js - which does this: 2 <code> 2 {{{ 3 3 destroyDescendants: function(/*Boolean?*/ preserveDom){ 4 4 // summary: … … 19 19 } 20 20 }); 21 </code> 22 21 }}} 23 22 24 23 However in 1.2.0 and later, the ContentPane does have a destroyDescendants() function which does this: 25 <code> 24 {{{ 26 25 27 26 destroyDescendants: function(){ … … 62 61 With this new change, if I remove and re-add a tree to a ContentPane, it fails to render. 63 62 64 </code> 63 }}}