You can do it in the following way: 1) Pure client side js handling 2) Using Ajax to update the components you are interested in.
Sergio García wrote: > > > > Alex Objelean wrote: >> >> There is a difference between a hidden component and invisible component. >> When component is not visible, it's markup is not rendered, thus the >> component is not validated. On the other hand, the hidden (in terms of >> css: visibility='hidden') means that markup is rendered and validated. >> >> Regards, >> Alex. >> >> > > Thanks. And, in wicket terms, ¿how can i make the textField within a > WebMarkupContainer hidden when a button is pressed? ¿Can I change > WebMarkupContainer css visibility from Wicket Java code? > > -- View this message in context: http://www.nabble.com/Form-componen-validation-on-invisible-components-tf4896386.html#a14024774 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
