Have you used div (dividers) HTML elements for the other form components
that have the correct styling?
I think a div tag break the inherited CSS similar to how table works.
Try to either use a span or apply the same style to div.
On a side note, if you want to support accessibility your label
Thanks, Paul.
The first div (profileTypeRow) has the correct styling. The only
difference between the profileTypeRow div and the oxeNodeRow div is
that profileTypeRow's visibility was never manipulated in the code, so it
is visible throughout while oxeNodeRow was initially hidden
Bors
-Original Message-
From: shimin_q [mailto:smq...@hotmail.com]
Sent: Monday, December 10, 2012 2:27 PM
To: users@wicket.apache.org
Subject: RE: Styling lost when a component is set visible during AJAX call
Thanks, Paul.
The first div (profileTypeRow) has the correct styling
The two divs are similar in the HTML:
div data-role=fieldcontain data-theme=b wicket:id=profileTypeRow
div data-role=fieldcontain data-theme=b wicket:id=oxeNodeRow
the data-theme attribute determines the style.
The wicket java code for the two divs are similar too, except the second div
was
it
might lose your data-theme attribute.
Anyhow, glad I could help you figure it out :)
~ Thank you,
Paul Bors
-Original Message-
From: shimin_q [mailto:smq...@hotmail.com]
Sent: Monday, December 10, 2012 3:14 PM
To: users@wicket.apache.org
Subject: RE: Styling lost when a component
