The accordion functions fine otherwise.

2. $('#campSessionEditorAccordionDiv').accordion({
3. heightStyle : 'content',
4. animate : {
5. easing : 'easeInExpo',
6. duration : 500,
7. down : {
8. easing : 'easeOutBounce',
9. duration: 500
10. }
11. },
12. create: function( event, ui ) {
13. console.log('create', ui.panel); // <- undefined
14. console.log('create', ui.header);
15. },
16. beforeActivate: function( event, ui ) {
17. console.log('beforeActivate', ui.newPanel);
18. console.log('beforeActivate', ui.newHeader);
19. }
20. });

On a related note - Should beforeActivate be fired when the first panel is opened automagically after initialization? It seems to me that it should be, but it's not. Just because that first panel is being activated programmatically doesn't mean the event shouldn't fire.

The only reason I even need the create event here is to grab that first panel after the accordion is loaded. Each panel contains a complex form and there are up to 30 of them.... I'd rather initialize them widgets (datepicker, etc) only as needed, eg - as each panel is actually activated.  That first panel needs the same work done on it as the others so getting a beforeActivate event firing on that would be handy (and appropriate in my not so humble opinion).

As it is, even if/when the create event gives me a valid ui.panel the code in my create event handler will be almost identical to me beforeActivate handler.  A "beforeFirstActivate' event would be nice to avoid this, and would also negate me needing to track which panel forms have already been initialized.. but I digress...