That's great! For tabbed panels that take a while to load I just apply lazy loading panels, that way that tab gets "loaded" immediately and an indicator is shown that the panel is being loaded. The user knows that the panel is being loaded and is unable to click any links on the "old" panel.
I handle it like how it's described here: http://www.mkyong.com/wicket/how-do-use-ajaxlazyloadpanel-in-wicket/ This also handles the scenario where non-JS enabled browser must be able to load the page (it's 2014 already, c'mon!). Cheers On Sunday, January 05, 2014 11:07:33 AM jchappelle wrote: > I have found the issue and I can finally reproduce it! > > The issue is similar to what you described. We have a dashboard panel that > has several tabs. Those tabs are ajax tabs. If a user clicks a tab and it > takes a while to load then they click on a link on the current tab while > waiting then you will get a ComponentNotFoundException. I tried to use the > "updateAjaxAttributes" approach by making custom tab links, but that didn't > work. Probably because the link they are clicking on the tab panel itself > does not have that attribute. > > My simple solution to this is to just use a regular TabbedPanel instead of > AjaxTabbedPanel. It seems to fix the issue. > > Thanks a bunch for your input because it pointed me in the right direction! > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Detecting-when-nothing-is-added-> > to-AjaxRequestTarget-tp4663469p4663477.html Sent from the Users forum > mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected]
smime.p7s
Description: S/MIME cryptographic signature
