You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org> on 2006/10/07 03:25:20 UTC
[jira] Assigned: (TAPESTRY-1109) Client Form validation validates
disabled fields
[ http://issues.apache.org/jira/browse/TAPESTRY-1109?page=all ]
Jesse Kuhnert reassigned TAPESTRY-1109:
---------------------------------------
Assignee: Jesse Kuhnert
> Client Form validation validates disabled fields
> ------------------------------------------------
>
> Key: TAPESTRY-1109
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1109
> Project: Tapestry
> Issue Type: Bug
> Components: JavaScript
> Affects Versions: 4.1.1
> Reporter: Greg Woolsey
> Assigned To: Jesse Kuhnert
> Priority: Minor
>
> Don't know if this is a bug or a "feature", and it appears to be down in DoJo, perhaps. But required and other field validations on the client side happen even if a field is disabled. Is that what we want? I'd expect that since disabled field data is not sent to the server anyway that validating them is unnecessary.
> The problem is that I have some form fields that are disabled if they are not required, but they are dynamically enabled and thus required based on values of other fields (a select, in particular, where some values require an additional field and others do not). Currently, I have to add my own custom validation profile to check if the fields are disabled first before performing standard validation. That's a bit cumbersome if I repeat the pattern on multiple pages.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org