You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org> on 2007/02/22 20:19:08 UTC

[jira] Commented: (TAPESTRY-1277) Select component requires a "value" binding even after an "id" binding has been specified

    [ https://issues.apache.org/jira/browse/TAPESTRY-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475125 ] 

Howard M. Lewis Ship commented on TAPESTRY-1277:
------------------------------------------------

The code appears to be in place for this, so it should work. It should have worked back in 5.0.1.  Are you sure your container had the matching property? I guess I'll add a test case to prove it works.

> Select component requires a "value" binding even after an "id" binding has been specified
> -----------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1277
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1277
>             Project: Tapestry
>          Issue Type: Bug
>    Affects Versions: 5.0
>            Reporter: Daniel Gredler
>            Priority: Minor
>             Fix For: 5.0
>
>
> Some form components like TextField don't require you to bind the "value" parameter if you specify the "id" parameter.
> The Select component does not yet follow this T5 rule of thumb.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org