The good thing also about setting the disabled property that on top of
adding the proper attribute, it should block any input in case you're
dealing with some smartass trying to circumvent the fact that the
client renders a field as read-only.
Eelco
On 11/7/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> On 11/7/06, ChuckDeal <[EMAIL PROTECTED]> wrote:
> >
> > We have the same kind of requirements for our app. We use the setEnabled
> > method of FormComponent to mark a field as disabled (setEnabled(false)),
> > then when it is rendered, it defaults to having the disabled attribute added
> > to the field. The only problem that we have noticed is that TextArea does
> > not work as we would like it when disabled because it becomes unscrollable,
> > instead we override the onDisabled() method of TextArea to set the readonly
> > attribute as well as a css style attribute ("color: GrayText;") to make it
> > appear disabled.
>
> Yep, that's exactly why
>
> protected void onDisabled(final ComponentTag tag)
>
> was introduced recently.
>
>
> Eelco
>
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
