myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Kienenberger" <mkien...@gmail.com>
Subject Re: disable, readonly bug
Date Thu, 30 Aug 2007 17:41:34 GMT
html disabled attribute means don't send the input field value back to
the server when the form is submitted.  If you want to be able to
change the field value, don't set the field disabled.  (or at least
use javascript to un-disable it before you submit the form)

On 8/30/07, Gargi Iyer <Gargi_Iyer@dcf.state.fl.us> wrote:
>
>
>
>
> I noticed that while using disable or readonly attributes of <t:inputText>
> or <h:inputText>, when the disable attribute changes from true to false and
> then value of the input text field is changed, the change does not take
> effect. When the disable attribute switches to true again, the old value is
> redisplayed and not the changed value.
>
> The setter methods of the property bound to the inputText  are not being
> called.
>
> This case arises only when the disabled attribute = true at page load time.
>
> I saw an entire application using value change listeners to call the field
> setter methods manually.  I think this totally ruins the fun in using JSF.
> Has anybody else noticed this behaviour? and does anyone have a solution
> for this?
>
> Thanks
>
> Gargi
> 850-414-5852
> CONFIDENTIALITY NOTICE:  This message and any attachments are for the sole
> use of the intended recipient(s) and may contain confidential and
> privileged information that is exempt from public disclosure.  Any
> unauthorized review, use, disclosure, or distribution is prohibited.  If
> you have received this message in error please contact the sender (by phone
> or reply electronic mail) and then destroy all copies of the original
> message.
>
>

Mime
View raw message