My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 329: Problem with allDay and end date
2 people starred this issue and may be notified of changes. Back to list
Status:  Done
Owner:  ----
Closed:  Feb 2010


Sign in to add a comment
 
Reported by yowza...@gmail.com, Feb 7, 2010
My backend REST service always outputs events with both start and end 
dates.  Assume this event for this discussion:

{
  "title":"Test",
  "start":"2010-02-05T00:00:00Z",
  "end":"2010-02-06T00:00:00Z",
  "allDay":false
}

Fullcalendar will display this event on a single day, but it will show the 
start and end times: 12a-12p Test

If I set allDay=true, then the times are no longer shown.  However, the 
event now spans across both 2/5 and 2/6. 

Since the event ends at midnight, technically it is into the next day.  But 
from a user's perspective, it would be better if it only showed up on 2/5.


Feb 7, 2010
Project Member #1 adamrs...@gmail.com
versions before 1.3 had the behavior you described. but the reason i changed it was 
because people who had all day events expected the end time to be inclusive. if the 
end was 2/6 they expected the all day event to run through it. and most often people 
just specify the date as '2010-02-05' or new Date(2010, 1, 5), which has a time of 
midnight.

i know the new way seems kind of weird, but it has resulted in less confusion. its 
actually the way google calendar does it too
Status: Done
Feb 7, 2010
#2 yowza...@gmail.com
I see your point, and it does make sense.  So I guess the only solution for me it to 
not mark these events as allDay.  Thanks.
Sign in to add a comment

Powered by Google Project Hosting