Changes between Initial Version and Version 1 of Ticket #5412


Ignore:
Timestamp:
Dec 18, 2007, 4:49:37 PM (12 years ago)
Author:
bill
Comment:

(FYI, I just cleaned up the formatting in your above post by adding the triple braces around code.)

You should be able to come up with a stand alone testcase for this, not involving EWD (or even involving a server... unless the problem is timing related, which is possible.)

Are you destroying the widgets before or after you null out innerHTML? If you destroy innerHTML first then maybe the widgets are getting confused.

Also, BTW, note that new Array() can (and should) simply be [], but in your case you don't want an array at all, but rather a hash, so you should replace new Array() with {} .

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5412

    • Property Cc rtweed@… removed
    • Property Reporter changed from guest to rtweed@…
  • Ticket #5412 – Description

    initial v1  
    99
    1010For the record, here's the example markup in the fragment I'm testing:
    11 
     11{{{
    1212   <div dojoType="dijit.layout.AccordionContainer" id="myAcc" style="overflow:auto;height:300px;width:400px;">
    1313      <div dojoType="dijit.layout.AccordionPane" id="accordion23" selected="true" title="Pane 1">blah blah blah</div>
     
    1515      <div dojoType="dijit.layout.AccordionPane" id="accordion33" title="Pane 3">khkjh hkhkh hjkhkh hjkhh hkjhhkjk</div>
    1616   </div>
     17}}}
    1718
    1819The fragment gets re-rendered by the following code that gets executed after this innerHTML is swapped into the container page:
    1920
     21{{{
    2022dojo.require("dijit.layout.AccordionContainer");
    2123// array of widgets that will need to be destroyed later
     
    2931dojo.parser.parse(dojo.byId('ewdthewholepage'));
    3032});
     33}}}
    3134
    3235and it's all cleaned up when you initiate another innerHTML swap by: