[
https://issues.apache.org/jira/browse/VALIDATOR-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511642
]
Martin Cooper commented on VALIDATOR-232:
-----------------------------------------
If we were talking about these words in a vacuum, I might agree with you, but
we are not. This is an attribute of a field. That field is going to be
scriptable, as in "able to be scripted", regardless of whether or not Validator
generates JavaScript code to validate the value of the field. In fact,
regardless of whether or not Validator does anything at all. Making a field
scriptable is not a function of Validator. Providing client-side validation, on
the other hand, is very much a part of what Validator does.
With regard to 'clientValidation' not describing the kind of client-side
validation, well, can you suggest other kinds of client-side validation that
someone might think of when they see that name, rather than JavaScript, and get
confused? If you want to get pedantic about the name, then 'scriptable' doesn't
do it either, because that name omits the scripting language, and also omits
whether the scripting will happen on the client or the server.
> Add script attribute to control script generation
> -------------------------------------------------
>
> Key: VALIDATOR-232
> URL: https://issues.apache.org/jira/browse/VALIDATOR-232
> Project: Commons Validator
> Issue Type: New Feature
> Components: Framework
> Reporter: Paul Benedict
> Priority: Minor
> Fix For: 1.4
>
> Attachments: VALIDATOR-232.dtd.patch, VALIDATOR-232.patch
>
>
> Add a script="true|false" attribute to <field> to control whether JavaScript
> should be generated.
> Also see: https://issues.apache.org/struts/browse/STR-1888
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
