Opened 14 years ago
Closed 13 years ago
#3620 closed bug (wontfix)
When yearRange rolls over, the resulting dates dont
| Reported by: | deebo | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.7 |
| Component: | ui.datepicker | Version: | 1.6rc2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
When using something like
yearRange: '-5:+0'
in december during year 2008, and you press 'next month' the calendar rolls over to 2003.
But if you select the date 1st of january 2003, the input field will contain '1st of january 2009' due to the rollover.
Change History (2)
comment:1 Changed 13 years ago by
| Milestone: | TBD → 1.6 |
|---|
comment:2 Changed 13 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
The yearRange setting only controls how many years show in the year drop-down. It does not restrict the selectable dates. You should use the minDate and maxDate settings for that, and the range of years in the drop-down will change accordingly. Note that the yearRange can also be set to absolute values, e.g. '2003:2008'.