Extra white space under merged event in Month view

[dandv]

[imightbeamy]

Hey @dandv, thanks for reporting this. Unfortunately, the limitation of this being an extension makes this issue hard to fix and it's unlikely that I'll be able to fix it well. That being said, whenever I get some time to look into it I will.

[pconwell-old]

I don't have a solution to this, but I had an observation. I was seeing the same issue, but completely unrelated to that issue, I changed my calendar's color then accidentally hid and unhid the calendar. Somehow in that process, when I refreshed the month view, it is now displaying correctly for me.

[bpearson]

@imightbeamy Can you still look into this? I have too many calendars to use the workaround and this can sometimes hide non-related events by the extra whitespace from the merged events.

Also on my cal, I can see the arrow for "not responded yet". And when you hover over the whitespace, the guest icon pops up.

[Shtutnik]

@bpearson pull request #25 should fix what you are seeing, from my understanding

[imightbeamy]

The arrow icons appearing is a separate issue from the extra whitespace. The arrows are a bug that need to get fixed, as I said before the pre-existing extra whitespace is limitation of this being an extension. Even if the whitespace was removed, it's complex to pull in the events that are hidden because they aren't loaded on the page until you click to see more on the day.

[Shtutnik]

I agree with @imightbeamy.
The only way to do this, in my opinion, is to put a hook on the function that enumerates the events before building the different views and to do the merge of the events in that context. This way, the events would be merged as objects in the code before the view is built, so the functions that build the view would "see" the already merged events, which will solve the issue mentioned here.
But since this extension's solution is built on the end-result view, developing such a technique would probably only be worth if a whole different extension were developed.

[dzoech]

Since this issue is from 2016 and in the meantime the new UI was introduced, I'd like to ask if the limitations stayed the same or if this is now possible to fix somehow.