My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 2397: Processing allDay events with time parts
1 person starred this issue and may be notified of changes. Back to list
Status:  ExportedToGithub
Owner:  ----
Closed:  Aug 2015


Sign in to add a comment
 
Reported by samedii, Dec 24, 2014
Is this the intended behaviour?

http://jsfiddle.net/3E8nk/920/

This becomes relevant when working with other libraries or such using different standards

I believe ending 1 one second early is how android does it. So for a "full two day event":
    "start": "2014-10-06T00:00:00.000Z",
    "end": "2014-10-07T23:59:59.000Z"
Jan 6, 2015
Project Member #1 adamrs...@gmail.com
As you have found, if the event is marked as all-day, but it's ISO8601 dates have time parts, the time parts are effectively ignored. This could be done more intelligently.

In the meantime, you could use eventDataTransform to help.
Summary: Processing allDay events with time parts (was: Edge cases: allDay date handling)
Status: Accepted
Labels: Type-Bug
Aug 21, 2015
Project Member #2 adamrs...@gmail.com
Discussion for this issue has moved to the following URL:
https://github.com/fullcalendar/fullcalendar/issues/2662

This is because Google Code is shutting down. Apologies if you are being pestered with these notifications. This is a one-time event.

Happy coding,
Adam
Status: ExportedToGithub
Sign in to add a comment

Powered by Google Project Hosting