Skip to main content

Search and Top Navigation

#5823 closed bug (invalid)

Opened July 13, 2010 02:45PM UTC

Closed November 02, 2012 09:14AM UTC

onChangeMonthYear not working properly with minDate and maxDate

Reported by: remington Owned by: remington
Priority: minor Milestone: 1.11.0
Component: ui.datepicker Version: 1.8.2
Keywords: Cc:
Blocked by: Blocking:

onChangeMonthYear recives the wrong date when working with a restricted date range.

This only happens when you switch the year(selecting it from the drop-down list) and the selected month is out of the datepickers range (in the year you selected).

onChangeMonthYear recives as paraeters the newly selected year and the selected month (the date isn't in the allowed range). The datepicker displays a different month (the first or last within the alowed range)

Attachments (0)
Change History (3)

Changed October 11, 2012 09:04PM UTC by scottgonzalez comment:1

milestone: TBD1.11.0

Changed October 18, 2012 05:14PM UTC by mikesherov comment:2

owner: → remington
status: newpending

Hi, Thanks for contributing! Could you possibly produce a or demonstration of the problem? I was unable to reproduce the issue myself.

Changed November 02, 2012 09:14AM UTC by trac-o-bot comment:3

resolution: → invalid
status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!