[
https://issues.apache.org/jira/browse/TAP5-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156365#comment-13156365
]
Lenny Primak commented on TAP5-805:
-----------------------------------
This issue also happens without clientValidation = false, and is a problem in
all instances of DateField
> DateField does not allow disabling of client-side validation, side-effects
> --------------------------------------------------------------------------
>
> Key: TAP5-805
> URL: https://issues.apache.org/jira/browse/TAP5-805
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.18
> Reporter: Gabriel RodrÃguez
>
> When using the DateField component in a form that has
> clientValidation="false" it will still bring up the floating validation
> popups for unparseable errors and will not allow using the calendar control
> (date-picker) until the text field is cleared of unparseable data. Because of
> this the end user will not be able to use the calendar control to fix the
> value entered until manually removing the bad value.
> On Tomcat 6, any browser after IE6.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
