Re: Disabling a form element server-side
Re: Disabling a form element server-side
- Subject: Re: Disabling a form element server-side
- From: Don Lindsay <email@hidden>
- Date: Thu, 12 Jun 2008 22:11:29 -0400
Hello;
The way I approach this is with a custom component I created with a
conditional component. If they do not have access to modify the
value, then it displays a string, otherwise it displays a listbox or
text box.
Don
On Jun 12, 2008, at 7:13 PM, Dan Grec wrote:
All,
We're currently using the "disabled" binding (and thus HTML) to stop
text entry into fields when a user doesn't have access.
(i.e. WOTextField, WOCheckbox, etc)
This presents a problem, as users can use an inline proxy or firebug
to submit the data anyway, which gets saved.
Our customers are complaining this is a security risk, so we have to
do something.
We're trying to come up with a way to handle the disabling on the
server side, rather than letter the browser deal with it.
We thought about conditionally rending them as a text equivelant (ie
WOString instead of WOTextField) but this will be pretty annoying
for WOCheckbox & WORadioButton.
Does anyone have any suggestions?
Thanks,
-Dan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@mac.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden