Changes between Initial Version and Version 1 of Ticket #10189


Ignore:
Timestamp:
Oct 23, 2009, 1:46:18 AM (12 years ago)
Author:
bill
Comment:

Please attach a test case using the attach file button.

The destroy() code you quoted is correct. AccordionContainer.destroy(), as specified in the definition of destroy() in _Widget.js, is supposed to destroy the AccordionContainer but not the children, where "children" means the underlying ContentPanes. The buttons, however, are part of the AccordionContainer and should be removed in the destroy() call.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10189 – Description

    initial v1  
    1 I found a bug in AccordionContainer. When I destroy an AccordionContainer and recreate later a new AccordionContainer with the same Id, I get the content of each child container at the same time and no headers have been displayed.
     1I found a bug in !AccordionContainer. When I destroy an !AccordionContainer and recreate later a new !AccordionContainer with the same Id, I get the content of each child container at the same time and no headers have been displayed.
    22This bug still exists in the version 1.3.2. I have looked at the code and have found the error (I changed the code and it is OK)
    33
    44The function in cause is :
     5{{{
    56destroy:function(){
    67dojo.forEach(this.getChildren(),function(_b){
    78_b._buttonWidget.destroy();
    89});
    9 
     10}}}
    1011the code is right except that this function should be named destroyRecursive to work correctly