[
https://issues.apache.org/jira/browse/VALIDATOR-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511455
]
Niall Pemberton commented on VALIDATOR-232:
-------------------------------------------
Not sure what you mean by "Because I don't have this ability, neither do I use
javascript at all on my Struts apps" - are you saying the lack of this feature
prevents you using javascript validation?
If theres a bug in one of the javascript validators then people would
presumably want to turn it off for all validations of that type (or override it
with their own custom javascript version with the bug fixed). I also don't
really see how switching on/off individual field's client validation has a use
for different intranet/internet deployments.
If the only use-case is the password scenario - then IMO would be more useful
to provide a password validator (combination of required, mix/max length and
mask) than this enhancement. If none of us have any other use case and the
users are not clamouring for it - then my preference is to not bother and focus
on other things instead.
> 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]
