Since upgrading the tabs from wiQuery 1.02 no longer work in my application.
Could be related as the CSS isn't being picked up at all. These are tabs on
panels displayed via ajax.
-----Original Message-----
From: Antoine Angenieux
Sent: Monday, November 29, 2010 8:42 AM
To: [email protected]
Subject: Wicket 1.4.14 > Bug with panels updated by Ajax rendering a CSS
Hi all,
I have just upgraded my dev environment from Wicket 1.4.13 to 1.4.14
this morning and discovered a bug related to CSS.
On a page, I have a panel containing a listview, itself populated with
panels that have in their constructor:
add(CSSPackageResource.getHeaderContribution(CSS));
When browsing to this page, the listview is initially empty. When the
panel is updated by an Ajax Link making the listview model list not
empty, the list view contents are rendered, but the CSS is not (and the
reference to the css script does not appear in the Wicket Ajax Debug
Window), and thus the presentation is all messed up.
I just downgraded back to Wicket 1.4.13, and all is fine.
I don't have time to prepare a Quickstart yet, but if anyone who has
been fixing bugs on Wicket 1.4.14 has a brilliant intuition on what can
cause this regression, it would be great ;)
Otherwise, I'll try to find sometime later this week to file a JIRA
issue with a Quickstart.
Cheers,
Antoine.
--
Antoine Angénieux
Associé
Clinigrid
5, avenue Mozart
75016 Paris, France
+336 60 21 09 18
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
