[
https://issues.apache.org/jira/browse/TRINIDAD-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737812#action_12737812
]
Cale Scholl commented on TRINIDAD-1538:
---------------------------------------
Code review changes:
var isStrict = ("DFMSWdhkHKmswy".indexOf(nextFormatType) != -1);
> Failing client side validation with some date patterns
> ------------------------------------------------------
>
> Key: TRINIDAD-1538
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1538
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 1.2.8-core
> Reporter: Lucas Satabin
> Attachments: 1.2.11.4-branch_dateFormat.patch, trunk_dateFormat.patch
>
>
> Some patterns can not be validated on the client side, using a
> convertDateTime component:
> Code to reproduce:
> <tr:inputDate value="#{bean.value}">
> <f:convertDateTime pattern="yyMMdd" />
> </tr:inputDate>
> If you choose a date in the calendar, the formatting works fine in the text
> field. But when you submit, you receive an error message saying: valid
> example: 981124
> This value obviously does not work either.
> A workaround is to disable the client validation with
> <client-validation>DISABLED</client-validation> but we loose the client
> message when something is wrong (the valid example)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
