v6-only bugfixes
- fix: non-string toolbar button text, like JSX, crashes rendering (#7120)
(now warns and falls back to the button name. use v7'siconContentfor custom button content) - fix: style injection crashes when calendar is mounted in an iframe (#7301)
- fix: crash when inline styles are blocked by a Content Security Policy (#7353)
(now warns instead. styles must be provided another way, or upgrade to v7, which distributes plain CSS files) - fix: crash in Salesforce LWC with Lightning Web Security when querying CSP nonce (#7439)
- fix: in list view, clicking event with url and custom eventContent crashes instead of navigating (#6133)
- fix:
batchRenderingmissing fromCalendarApitype, e.g. for React'sgetApi()(#7227)
Bugfixes backported from v7
- fix:
event.setProp('resourceEditable', ...)ignored with a warning (#5166) - fix: React "Maximum update depth exceeded" when
validRange,visibleRangeorhiddenDaysis a new-but-equal value each render anddatesSetsets state (#7069) - fix: when
slotMaxTimeis beyond 24h, now-indicator disappears after midnight in timeline views, and its arrow disappears in timegrid views (#6394) - fix:
eventDropreportsoldResource/newResourcewhen an event that isn't resource-editable is dragged over another resource, even though its resource doesn't change (#4943) - fix: event time cut off by long title with eventDisplay:'block' (#6457)
v7 upgrade guidance
- feature: passing a v6 plugin to FullCalendar v7 now fails with a clear message naming the v7 import
(v6 plugins carry amajorVersionErrorproperty. in TypeScript, the error replaces a cryptic one aboutpremiumReleaseDate) - docs: READMEs and npm descriptions of the v6-only packages, like
@fullcalendar/daygrid, now say they're for v6 and name their v7 replacement