Hi Shannon, Is this on a stateful page? If so please note that stateful pages have been deprecated in 2.3.0 (they had many issues) and replaced with stateful controls.
The fact that the inner tabbedPanel does not navigate seems to indicate that they aren't reachable for the Page to process them. Either the inner panel is not added to the outer panel or the AutoBinding feature is used which automatically added the inner panel to the Page. There might be a change in the autobinding in 2.2.0 which triggers the new behavior. My suggestion is to limit the use AutoBinding as it is quite confusing. If the inner panel is a public variable, change it to private and add it manually to the outer panel. Kind regards Bob On 2011/02/14 19:21 PM, sdiener wrote: > > Hi! > > I have a Page containing a TabbedPanel where one of the tabs in the > TabbedPanel is a Panel that contains another TabbedPanel. > > This worked great for Click 2.1.0, but when I upgraded to Click 2.2.0 I > suddenly couldn't switch tabs in the inner TabbedPanel (the outer > TabbedPanel still worked correctly). I could see the inner TabbedPanel's > tab's link address show up correctly when the mouse hovered over the tab but > when I clicked on the tab nothing seemed to happen. I found that if I added > the inner TabbedPanel to the Page using addControl (even though it isn't > called out in the Page htm, but is instead called out in the Panel's htm) > that tab switching worked as expected again. > > My problem seemed to be solved until I tried to click Submits and > ActionLinks in the inner TabbedPanel's Panels. These appeared to work fine, > at first, until I selected and submitted a request in one of the other outer > TabbedPanel's Panels and then went back to the inner TabbedPanel's Submits > and ActionLinks where the requests seemed to be ignored. > > It looked like part of the problem was that when I returned to the inner > TabbedPanel after performing an action in another of the outer TabbedPanel's > Panels that the HEAD Elements needed for the inner TabbedPanel weren't being > updated in the page (I didn't see them in the source). But if I were to > refresh the inner TabbedPanel, like by switching tabs in the inner > TabbedPanel, it seemed that it found what it needed and everything worked > correctly again. > > I was able to work around this second problem by listening for the selection > of the outer TabbedPanel's tab that contains the inner TabbedPanel. Then > using setActivePanel on the inner TabbedPanel to select the tab that was > already selected - which seemed to perform a refresh. > > I'm fairly new to Click and I'm not sure that my workarounds to the problems > listed are the best. Is there a better solution to these issues? > > Also, I was hoping to find out what happened between Click 2.1.0 and Click > 2.2.0 that caused this change in functionality. I read that the old HTML > imports were removed in favor of the new HEAD elements. But I'm not using > the old getHtmlImports method in my code, so I'm not sure what went wrong. > > Thanks for your help!
