[
https://issues.apache.org/jira/browse/TRINIDAD-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799713#action_12799713
]
Carsten Pieper commented on TRINIDAD-37:
----------------------------------------
If anyone else than me is listening, this is what I found out:
The patch made it into the code base but hasn't been made public. This might be
the reason why it hasn't been made browser-safe... The situation for the
browsers available to me:
onblur="_validateInput(event);" works for Firefox
onblur="_validateInput(window.event);" works for IE (6 to 8) and Google Chrome
> 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
> Attachments: autoSubmit.patch
>
>
> 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.
