#5285 closed bug (duplicate)
datepicker.parseDate doesn't handle short years properly
| Reported by: | Ivan Peters | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | ui.datepicker | Version: | 1.7.2 |
| Keywords: | parseDate | Cc: | |
| Blocked by: | Blocking: |
Description
The parseDate code appears to cheat slightly by assuming that each component will use the maximum number of digits or will have some sort of delimiter. In the case of the year, it assumes up to 4 digits which can be a problem for dates using this format:
yddmm
$.datepicker.parseDate("yddmm", "100105") will fail with "Missing number at position 6".
Change History (4)
comment:1 Changed 12 years ago by
comment:2 Changed 12 years ago by
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Thanks, closing as a duplicate.
Note: See
TracTickets for help on using
tickets.
This should have been resolved by the fix for #6659.