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 (setVisible(false)) then setVisible(true) in the ajax update call. So I think the styling got lost when I set the div visible again. If I took out the setVisible(false) and setVisible(true) for "oxeNodeRow", it did show up with the correct styling.
Do you think I need to call some other methods in addition to setVisible(true) to get the style applied to the newly visible <div>? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Styling-lost-when-a-component-is-set-visible-during-AJAX-call-tp4654656p4654663.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
