Closed GoogleCodeExporter closed 9 years ago
If the end date is the same as the start date, you don't need to specify an end
date.
It will show without needing to list an hour. That is a temporary way of getting it
to work without a time. Strange bug though.
Original comment by jstrong...@gmail.com
on 9 Jun 2009 at 7:37
by design, end dates in fullcalendar are exclusive. so, if your event is 2 days
long,
it will end on midnight of the second night (00:00:00 of the 3rd day). this
allows
the span to be exactly 48 hours. this is an approach commonly used by
date/calendar
software.
When you specify the start + end date to be exactly the same, you are
effectively
saying your event is instantaneous and spans no time. a way to fix this, as
jstrong
pointed out, is to omit the end time, which causes fullcalendar to pick an end
time
of midnight.
fullcalendar simply won't display an event w/ no timespan. however, i do not
like
this behavior. I will classify this as a bug. even if the timespan is zero, the
event
should still be displayed. i will fix this in the next patch-level release.
Original comment by adamrs...@gmail.com
on 17 Jun 2009 at 2:33
yep, ive also encountered this bug but bug appears only in IE though
Original comment by albert.o...@gmail.com
on 19 Jun 2009 at 6:39
made this failsafe in the new version 1.2.1. the event will now be displayed
and no
errors thrown. but still remember, end dates need to be EXCLUSIVE
(http://arshaw.com/fullcalendar/docs/#calevent-objects)
Original comment by adamrs...@gmail.com
on 30 Jun 2009 at 6:29
Original comment by adamrs...@gmail.com
on 14 Aug 2013 at 2:11
Original comment by adamrs...@gmail.com
on 14 Aug 2013 at 2:12
Original issue reported on code.google.com by
info%xyl...@gtempaccount.com
on 9 Jun 2009 at 11:06