[
https://issues.apache.org/jira/browse/TRINIDAD-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498103
]
Adam Winer commented on TRINIDAD-37:
------------------------------------
What would be best is if inline validation always fired with onblur/onchange,
and it got set up without requiring users to explicitly set any onchange or
onblur on the input components.
> Client-side validation should support onblur/onchange validation when set to
> 'inline'
> --------------------------------------------------------------------------------------
>
> Key: TRINIDAD-37
> URL: https://issues.apache.org/jira/browse/TRINIDAD-37
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Components: Components
> Reporter: Danny Robinson
> Priority: Minor
>
> The 'inline' client-side validation should support the ability to validate
> fields on-the-fly when the user navigates away from the field. This was
> provided in the recent 'inline' patch using the validateInput() method, but
> was made private until we make some further improvements.
> Just created this email to keep track of the issue.
> Pasted from email:
> Adam said: The JS validateInput() method has been made private, because I'd
> like to start putting JS methods on namespace objects instead of putting it
> in the window object - and it only supports inline validation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
