Search and Top Navigation
#4078 closed bug (duplicate)
Opened February 06, 2009 08:03PM UTC
Closed February 19, 2009 10:50AM UTC
Last modified October 03, 2012 04:54PM UTC
Unspected behaviour whin month/year menu, date range and view multiple months
Reported by: | cocotapioca | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 1.6 |
Component: | ui.datepicker | Version: | 1.6rc6 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
someInput.datepicker({ buttonImage: imgPath, buttonImageOnly: true, showOn: 'button', minDate: 0, maxDate: '+11M', // so end range is in january of the next year clearAtTop: false, firstDay:1, dateFormat:'yy-m-d', numberOfMonths:2 }
With this setup and today month as reference date (02/09), when the user select 2010 from the year dropdown, the calendar displays december 2009 and january 2010, now try to select some other month using the month dropdown (the year dropdown is in 2009), the calendar remains in the same months (december and january). This is happening because of range comparation and that the calendar believes that it should be displaying a month in 2010(which is partially true).
Attachments (0)
Change History (3)
Changed February 12, 2009 11:46PM UTC by comment:1
description: | someInput.datepicker({ \ buttonImage: imgPath, \ buttonImageOnly: true, \ showOn: 'button', \ minDate: 0, \ maxDate: '+11M', // so end range is in january of the next year \ clearAtTop: false, \ firstDay:1, \ dateFormat:'yy-m-d', \ numberOfMonths:2 \ } \ With this setup and today month as reference date (02/09), when the user select 2010 from the year dropdown, the calendar displays december 2009 and january 2010, now try to select some other month using the month dropdown (the year dropdown is in 2009), the calendar remains in the same months (december and january). This is happening because of range comparation and that the calendar believes that it should be displaying a month in 2010(which is partially true). → {{{ \ someInput.datepicker({ \ buttonImage: imgPath, \ buttonImageOnly: true, \ showOn: 'button', \ minDate: 0, \ maxDate: '+11M', // so end range is in january of the next year \ clearAtTop: false, \ firstDay:1, \ dateFormat:'yy-m-d', \ numberOfMonths:2 \ } \ }}} \ With this setup and today month as reference date (02/09), when the user select 2010 from the year dropdown, the calendar displays december 2009 and january 2010, now try to select some other month using the month dropdown (the year dropdown is in 2009), the calendar remains in the same months (december and january). This is happening because of range comparation and that the calendar believes that it should be displaying a month in 2010(which is partially true). |
---|---|
milestone: | TBD → 1.next |
Changed February 19, 2009 10:50AM UTC by comment:2
resolution: | → duplicate |
---|---|
status: | new → closed |
Duplicate of #3778. Fixed in r1673.
Changed October 03, 2012 04:54PM UTC by comment:3
milestone: | 1.next → 1.6 |
---|