Hey thanks for trying it. My tabs are on panels that get swapped in and out
via ajax. Are you using this approach? Since our app creates these tabs
dynamically via ListViews, I thought maybe it was my implementation. As a
test I took the most basic tab example from the wiQuery site and put it on a
panel displayed via ajax when a link is clicked. It's not working either. If
I go back to 1.4.12, it works fine.
I'll poke around a little with Firebug but I'm guessing the css and perhaps
javascript aren't being contributed in my scenario.
-----Original Message-----
From: Brian Topping
Sent: Monday, November 29, 2010 12:27 PM
To: users@wicket.apache.org
Subject: Re: Wicket 1.4.14 and WiQuery Tabs
On Nov 29, 2010, at 12:04 PM, Brad Grier wrote:
After 1.4.14 wiquery tab components no longer render in my application.
These tabs are sitting on panels displayed via ajax so perhaps it’s
something to do with the css/javascript contribution. Interestingly the
wiquery accordions still work fine.
Since I was due to upgrade this as well and am using both wiquery accordions
and tabs, I thought I would give it a try. My tabs are on panels that are
triggered by selections in the accordions (hey, are we working on the same
source tree? ;-)). But I'm unable to replicate this, everything is
rendering fine.
If I can assist by checking any specific rendering or you want a snippet of
the HTML that's being generated on my end to help you debug, feel free to
contact me off-list.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
