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)" <de...@tapestry.apache.org> on 2008/08/27 04:01:44 UTC
[jira] Closed: (TAPESTRY-2575) Disabled fields still perfom client
side validation in 5.0.13
[ https://issues.apache.org/jira/browse/TAPESTRY-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-2575.
------------------------------------------
Resolution: Invalid
Fix Version/s: (was: unspecified)
Assignee: Howard M. Lewis Ship
You do have to manage the disabled flag on the client and the server correctly, as you observed. This is because the disabled status of the field may change dynamically due to client-side JavaScript. Often a hidden form field is used to synchronize the state.
> Disabled fields still perfom client side validation in 5.0.13
> -------------------------------------------------------------
>
> Key: TAPESTRY-2575
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2575
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.13
> Reporter: Sean Redmond
> Assignee: Howard M. Lewis Ship
>
> When disabling Fields (eg. TextField) by setting disabled=true to use them as displaying only components, those components still perform client side validation and show error messages
--
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