Issue 385: Render events within DST gaps
Status:  Released
Owner: ----
Closed:  Jun 2014
Reported by katie.e....@gmail.com, Mar 10, 2010
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
sorry for the delay katie. i see what you mean. the event changes in length based on where it is dropped b/c, when no end time is specified, it defaults to the start time + 2 hours. if this implicit end time falls in the "dead zone" caused by dst, it is moved back to 2am, thus appearing to shorten.

i dont know how to solve this problem (especially since it semantically makes sense) other than to have an option to "turn off" DST gaps, which would be difficult, because JS's native Date object's behavior cannot be changed and it is baked into fullcalendar. if i hear more complaints about this i will consider it further.
Summary: Render events within DST gaps
Oct 7, 2010
Project Member #2 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Maybe
Sep 14, 2011
#3 mreco...@gmail.com
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
#4 GustavoS...@gmail.com
Same problem here..
Aug 13, 2013
Project Member #5 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Accepted
Labels: Type-Bug
Aug 15, 2013
Project Member #6 adamrs...@gmail.com
 Issue 1441  has been merged into this issue.
Sep 1, 2013
Project Member #7 adamrs...@gmail.com
(No comment was entered for this change.)
Labels: milestone-date
Jan 25, 2014
Project Member #8 adamrs...@gmail.com
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
Project Member #9 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Implemented
Jun 2, 2014
Project Member #10 adamrs...@gmail.com
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
#11 m.yaskev...@paralect.com
This wasn't fixed in v2.2.7! Any clues?