[TAPESTRY-2047] Client side date validation doesn't accept mixed case am/pm strings

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.1.3
• Fix Version/s: 4.1.5
• Component/s: JavaScript
• Environment: browser
• Assignee: Jesse Kuhnert
• Reporter: Jesse Kuhnert
• Created: 15/Jan/08 17:39
• Updated: 15/Jan/08 17:41
• Resolved: 15/Jan/08 17:41

Description

Given an input string of "1:30 aM" and pattern "h:mm a" the current client side validation fails because it doesn't handle mixed case for the am/pm portion.