You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Try to type any november date prior to 2009, like 2007-11-07, and all calendar's cases will be filled by the same number (28 for this example). Works the same way on FF or IE.
As the previous issues were posted several months ago, is there a chance to get an answer, or even an hint to fix the problem ourselves ?
The text was updated successfully, but these errors were encountered:
The issue is with Daylights savings.
ie: Nov 1, 2009 to Nov 2nd, Daylights savings means Nov 1 + 24 hours of seconds gets you to Nov 1, 23:00. Because it sets the hour, Nov 1 23:00 becomes Nov 1, 00:00, and you end up repeating the date.
Ended up adding a bit of code to fillCalendar method:
@@ -13629,13 +13629,15 @@ var DatePicker;
});
document.id(this.rows[0].getElements('td')[1]).empty().adopt(monthyr);
var atDate = startDate.clone();
+ // deal with a daylight savings time issue, see: Nov 1st, 2009
+ var incrementTime = Date.units.day() + (Date.units.hour() * 2);
this.rows.each(function(row, i){
if (i < 2) return;
row.getElements('td').each(function(td){
atDate.set('hours', hours);
td.firstChild.data = atDate.getDate();
td.refDate = atDate.getTime();
- atDate.setTime(atDate.getTime() + Date.units.day());
+ atDate.setTime(atDate.getTime() + incrementTime);
}, this);
Hi there,
As mentionned here http://github.com/anutron/clientcide/issuesearch?state=open&q=datepicker#issue/15 and here http://github.com/anutron/clientcide/issuesearch?state=open&q=datepicker#issue/26 some dates break the DatePicker.
I'm sure that's an issue, as you can reproduce the bug in the tutorial/demo section here :
http://www.clientcide.com/wiki/cnet-libraries/09-forms/02-datepicker
Try to type any november date prior to 2009, like 2007-11-07, and all calendar's cases will be filled by the same number (28 for this example). Works the same way on FF or IE.
As the previous issues were posted several months ago, is there a chance to get an answer, or even an hint to fix the problem ourselves ?
The text was updated successfully, but these errors were encountered: