I having a problem loading a form into an accordion pane. The form is defined in an external html document that I am loading via the href attribute on the accordion pane. I can open the panel1.html document directly and no errors are reported by by firebug. However, when I embed the form in an accordion pane, I get the following error from firebug and the form doesn't render correctly. I've noticed that if I include the dojo.require()'s that are declared in panel1.html directly in accordion.html then things seem go better.

I have some script that programatically creates AccordionPanes based on information it finds via a datastore. I inserted in some alerts such that I could debug the code. It works with the alert in place ... however when I remove the alert statement, only one of the AccordionPanes (the selected one) is visible. I have looked at the generated page source, and the other AccordionPanes are being generated .. they just are not visible.

Here is my script:

dojo.addOnLoad(function() {
// Get the datasource description for the accordion panes

Why doesn't the children resize when I do the following? The main accordion container adapts but the accordion panes stay the exact same size.

This is the code after I set new content into a neighboring contentpane setting the heigh of the parent div.

var accordion = dijit.byId('my_accordion_div_id');
if(accordion){
	accordion.layout();
}

While working with Layout Widgets i noticed that if there are layout items within an accordionPane they do not get resized or have their layout correctly rendered. Looking into the source code it appears that it is a todo item to have the accordionPane call the resize function of its nested containers. Below are the changes i made to have the child layouts resize.

Be warned, I have not fully tested the solution on all cases!

When i place a Text box in an accordion container with some text in it and try to move the cursor in the textbox using Left and Right arrow keys of the keyboard, the accordion pane animation happens rather than the cursor to move inside the text box.

Is this the normal behavior of this widget? If not how to avoid this?