myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo Uribe (JIRA)" <...@myfaces.apache.org>
Subject [jira] Commented: (MYFACES-1898) Dynamic disabling of UIInput component doesn't work correctly
Date Tue, 29 Jul 2008 14:36:32 GMT

    [ https://issues.apache.org/jira/browse/MYFACES-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617799#action_12617799
] 

Leonardo Uribe commented on MYFACES-1898:
-----------------------------------------

According to the spec set disable=false does not stop to be executed the process validations
and update model phases. If you want this behavior, use rendered property instead. 

This issue will be closed as invalid. Thanks for the observations.

> Dynamic disabling of UIInput component doesn't work correctly
> -------------------------------------------------------------
>
>                 Key: MYFACES-1898
>                 URL: https://issues.apache.org/jira/browse/MYFACES-1898
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 1.2.3
>         Environment: MyFaces 1.2.3, Spring WebFlow 2.0.2, RichFaces 3.2.1, Tomahawk 1.1.6,
Facelets 1.1.15.B1, Tomcat 6.0.16
>            Reporter: Patrick Schmidt
>         Attachments: example.zip
>
>
> See the attached example.
> I have an h:inputText, which is disabled depending on the value of the property fieldDisabled.
This property is changed in a toggle-action method. The toggleDisableButton, which triggers
this action has an immediate=true set. Therefore it is possible to disable the h:inputText,
even if it is still invalid respectively has no value set.
> The problem is that after clicking the toggleDisableButton the h:inputText is rendered
disabled as intented. However if afterwards the form is submitted by the submit-button, then
the validation and updateModel still runs for the h:inputText. Although it shouldn't for disabled
components.
> I am not quite sure, if this is a bug or consistent with the jsf-spec. However the same
example works, if the h:inputText is dynamically rendered instead of disabled. And at least
the behaviour should then be consistent, shouldn't it?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message