Error when eventContent is providing domNodes as a view-specific option then switching to a view that does not have eventContent defined

[divya-sk-tfs-zz]

Reduced Test Case: https://codepen.io/divyask53/pen/QWKZYQq?editors=001

Bug Description

1. open the codepen link https://codepen.io/divyask53/pen/QWKZYQq?editors=001
2. initial view is set to dayGridMonth (initialView: 'dayGridMonth)
3. click dayGridWeek (week view)
4. by clicking back or prev button in week view, move to the week view which has got events for that particular week
   for example we have events on July 14 and July 18 2021, so move to Jan 10 – 16, 2021 range in week view
5. now click month view
   6)in console we get the below error
   Uncaught TypeError: Cannot convert undefined or null to object
   at slice ()
   at Object.Yo [as render] (main.min.js:6)
   at t.updateCustomContent (main.min.js:6)
   at t.componentDidUpdate (main.min.js:6)
   at t. (main.min.js:6)
   at main.min.js:6
   at Array.some ()
   at main.min.js:6
   at Array.some ()
   at P (main.min.js:6)

Screenshot:

[acerix]

Thanks, confirmed.

The bug seems to happen when eventContent is providing domNodes as a view-specific option then switching to a view that does not have eventContent defined. I simplified the demo to show the error just by switching to month view:

https://codepen.io/acerix/pen/QWKJyPN?editors=0010

It can be fixed by supplying eventContent for all views or having a default:

https://codepen.io/acerix/pen/PoGxNYo?editors=0010

Also reported in https://fullcalendar.freshdesk.com/a/tickets/2565

[divya-sk-tfs-zz]

Hi,

thanks for the update, after addition of default event content, we cannot see the error,

but we have some logic written in dayCellDidMount in month view, and we see some dates are not called in dayCellDidMount in month view, when switched from week view to month view
opened a new ticket regarding this issue

#6089

can u please look into this.

[arshaw]

reproduced. update repro.

[arshaw]

I thought I fixed this in 5.9.0 ... (updated repro) ...

But as you can see in the new repro the content from one view makes its way into the other (along with some DOM mangling). I will fix in the next release.

[vladdnepr]

Confirmed. After update to 5.9 I cant reproduce bug. All is OK

[arshaw]

I fixed the JS error from happening back in July with v5.9.0, however, the domNodes were still not cleared when switching views.

v5.10.0 fixes the entire problem.

Updated repro: https://codepen.io/arshaw/pen/XWRENao?editors=0010