You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Henri Yandell (JIRA)" <ji...@apache.org> on 2007/08/15 07:35:30 UTC

[jira] Commented: (VALIDATOR-207) Disabled fields should not be checked by the validateRequired function. Relevant to adding the check for field disabled in jcv_isFieldPresent.

    [ https://issues.apache.org/jira/browse/VALIDATOR-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519864 ] 

Henri Yandell commented on VALIDATOR-207:
-----------------------------------------

I'm +1 to improve the docs to mention this change, and close this as WONTFIX.

> Disabled fields should not be checked by the validateRequired function.  Relevant to adding the check for field disabled in jcv_isFieldPresent.
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: VALIDATOR-207
>                 URL: https://issues.apache.org/jira/browse/VALIDATOR-207
>             Project: Commons Validator
>          Issue Type: Bug
>          Components: JavaScript
>    Affects Versions: 1.3.0 Release
>            Reporter: Joseph Breuer
>
> For validateRequired the following condition checks to see if the field is present.  It then sets the validity to false.
>             if (!jcv_isFieldPresent(field)) {
>                 fields[i++] = oRequired[x][1];
>                 isValid=false;
>             }
> Supposedly validateRequired as well as all of the validate methods are not supposed to validate fields that are set as disabled.  This method seems to categorize disabled fields with those that are null or are undefined.
> validateRequired should differentiate between the disabled fields and the not present fields.

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