Control over how multi-day timed events rendering their time text

[flack]

Steps to reproduce:

1: go to http://fullcalendar.io/js/fullcalendar-2.6.0/demos/selectable.html
2: go to week view
3: select a timespan from Monday to Tuesday

Expected result:

• selected end time is shown on fc-event-helper

Actual result:

• 12:00 is shown, no matter when the event actually ends

Screenshot:

[arshaw]

this was intentional behavior for events that span across the nextDayThreshold. If you scroll up you'll see the event on Monday continue from midnight to 9am on Tuesday.

If there is enough demand, we could potentially introduce a setting for fine-grain control of this behavior.

[flack]

hmm, ok, but if it's intentional, then why do I get a different end time in event.end when the eventDrop callback runs? In the screenshot above, event.end will be 9:00 AM, it's only the displayed value on the helper that says 12:00

[arshaw]

this issue concerns itself with how an event's text is displayed. concerned with what text renders on each event segment when it spans across two days. It's merely what text is displayed. the underlying data, the event.end should be as expected.

[ghost]

I, too, would like this functionality. It would be nice to have the option of whether to show the splits or the actual event time on both segments.

[jayatulsiani]

yes i would like this functionality to be implemented. can it be done using range option? i tried using range but in vain. can somebody help me here

[bartvdklu]

It would be nice to have this functionality! Hope it gets implemented. 👍

[blissdev]

This would be very useful for my team's usage.

[ekrismer]

I've found at least four locations that are affected by this issue.

Have a look at this Codepen: https://codepen.io/erabl/pen/GRXgNVm

1. Multiday events that exceed the current view's date range, but start/end within
   

2. Multiday events that start before and end after the current view's date range
   

3. Multiday events that are part of a '+ more' popover
   

4. Multiday events in a timeGrid
   

I was able to find a workaround to show the actual start/end time of the events for v5.11.0 (Codepen) using

eventContent: (arg) => {
  if (arg.event.start && arg.event.end) {
    // this is just a quick hack: use a proper date formatter with timezone!
    arg.timeText = `${arg.event.start.toISOString().slice(11,16)} - ${arg.event.end.toISOString().slice(11,16)}`;
  }
}

but could not get this to work with v6.1.4.

@arshaw, @acerix do you know a workaround that is compatible with v6?

Are there any plans to add a flag that controls how multiday event times are rendered?

Possibly related issues: #6936, #3765, #5826.

[ekrismer]

I figured out a workaround for v6.1.0: Content Injection now requires to return true to render the default content (see #7110 and https://fullcalendar.io/docs/upgrading-from-v5#content-injection).

eventContent: (arg) => {
  if (arg.event.start && arg.event.end) {
    // this is just a quick hack: use a proper date formatter with timezone!
    arg.timeText = `${arg.event.start.toISOString().slice(11,16)} - ${arg.event.end.toISOString().slice(11,16)}`;
  }
  return true; // render default content
}

This hint unfortunately is not mentioned in the regular documentation: https://fullcalendar.io/docs/content-injection