You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Igor Drobiazko (JIRA)" <ji...@apache.org> on 2009/10/27 09:02:59 UTC

[jira] Closed: (TAP5-906) t:disbled property of input components does not work correctly with property binding

     [ https://issues.apache.org/jira/browse/TAP5-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Drobiazko closed TAP5-906.
-------------------------------

       Resolution: Cannot Reproduce
    Fix Version/s: 5.1.0.5

I tried to reproduce the described behaviour with Tapestry 5.1.0.5 and was not successful. If the problem still exists please provide a sample page.

> t:disbled property of input components does not work correctly with property binding
> ------------------------------------------------------------------------------------
>
>                 Key: TAP5-906
>                 URL: https://issues.apache.org/jira/browse/TAP5-906
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Erich Gormann
>            Priority: Critical
>             Fix For: 5.1.0.5
>
>
> When setting a t:disabled attribut into an input component like t:select or t:textfield and proving its value as property expression binding, the field is allways threated as disabled. Even when providing the value "false" for the expression. 
> When setting "false" via literal binding t:disabled="literal:false" all works fine. 

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