Adam Shaw

OR, you could use one of these two solutions: - [ontransitionend](https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers/ontransitionend) - [ResizeObservable](https://developer.mozilla.org/en-US/docs/Web/API/ResizeObserver) FullCalendar was never designed to be completely resizable via CSS. There is always some JS that needs...

I believe this is fixed in [v7.0.0-beta.0](https://github.com/fullcalendar/fullcalendar-workspace/releases/tag/v7.0.0-beta.0) but I don't have a clean repro to be able to update and prove it's fixed. @adenta, would you be able to check?

Fixed in [v7.0.0-beta.0](https://github.com/fullcalendar/fullcalendar-workspace/releases/tag/v7.0.0-beta.0)

Reopening this issue because it's distinct from #7488. This issue is related to the React `key` on `fc-daygrid-event-harness` being frequently invalidated. @Aleafan, I began addressing this in the v7 beta...

I'm actually questioning this now. @Aleafan, you say `instanceId` is changing every render... but `instanceId` would only change if a distinct new event object is given, thus resulting in new...

This has been improved in [v7.0.0-rc.0](https://github.com/fullcalendar/fullcalendar-workspace/releases/tag/v7.0.0-rc.0), please see [this comment in another issue](https://github.com/fullcalendar/fullcalendar/issues/3003) for more details.

The optimizations I mentioned in [this comment](https://github.com/fullcalendar/fullcalendar/issues/3003#issuecomment-2675636273), which was meant for v7, have been backported to v6. See the [v6.1.18](https://github.com/fullcalendar/fullcalendar/releases/tag/v6.1.18) release. Updated repro demonstrating that only modified events are rerendered:...

As of v5, when switching between views of the same parent type, the DOM will be reused and the viewDidMount/WillUnmount will NOT fire. I need to document this better.

Reported by `adamrshaw` on 2014-08-07 20:10:08 - **Status changed**: `Reproducing` - **Labels added**: Type-Bug

``` I can confirm this bug exists. However, it is also present in pre-2.1, so I will not fix it for the 2.1 release. Will get to it at some...