| Issue 385: | Render events within DST gaps | |
| 8 people starred this issue and may be notified of changes. | Back to list |
In a bug that may be related to Issue 206 , putting a date on the calendar on the 14th of March, 2010 (which is the cut over to daylight savings time in the US this year) results in problems for any event which occurs during the change-over hour of 2 a.m. The next day appears to be fine, as do all preceeding days. This occurs when adding an event via callbacks using click from standard time. The event snaps back (or, I assume in the lost hour at the other side of the change, forward) an hour. This behavior makes sense once you think about it, but otherwise is quite confusing. Is there a way to specially mark or limit these hours? I know timezone conversion is a big hassle, but for users it could be confusing to have the automatic behavior. It doesn't help that the event seems to get arbitrarily long when that happens.
Jun 14, 2010
Project Member
#1
adamrs...@gmail.com
Summary:
Render events within DST gaps
Oct 7, 2010
(No comment was entered for this change.)
Status:
Maybe
Sep 14, 2011
Same problem here. In the 3th week of october, all events in the first slot are gone. Any suggestions? I can try to go into fullcalendar.js if you point some directions... (using v 1.5)
Nov 1, 2011
Same problem here..
Aug 13, 2013
(No comment was entered for this change.)
Status:
Accepted
Labels: Type-Bug
Aug 15, 2013
Issue 1441 has been merged into this issue.
Sep 1, 2013
(No comment was entered for this change.)
Labels:
milestone-date
Jan 25, 2014
Just released 2.0.0-beta, which makes progress on a new timezone system, which will solve this issue: http://arshaw.com/fullcalendar/docs2/
May 25, 2014
(No comment was entered for this change.)
Status:
Implemented
Jun 2, 2014
version 2 has been released with this change. http://blog.arshaw.com/1/post/2014/06/fullcalendar-2-released.html
Status:
Released
Oct 7, 2015
This wasn't fixed in v2.2.7! Any clues? |
|
| ► Sign in to add a comment |