Changes between Initial Version and Version 5 of Ticket #7959


Ignore:
Timestamp:
Nov 5, 2008, 1:31:32 AM (14 years ago)
Author:
bill
Comment:

Yup, this is a dup of #7784. I'll add Josh to the CC there.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #7959

    • Property Owner set to Sam Foster
    • Property Status changed from new to closed
    • Property Resolution changed from to duplicate

  • Ticket #7959 – Description

    initial v5  
    11In 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{{{
    33        destroyDescendants: function(/*Boolean?*/ preserveDom){
    44                // summary:
    … …  
    1919                        }
    2020                });
    21 </code>
    22 
     21}}}
    2322
    2423However in 1.2.0 and later, the ContentPane does have a destroyDescendants() function which does this:
    25 <code>
     24{{{
    2625
    2726        destroyDescendants: function(){
    … …  
    6261With this new change, if I remove and re-add a tree to a ContentPane, it fails to render.
    6362
    64 </code>
     63}}}