Chrome 91 update causes incorrectly positioned lines in timeline v4
See original GitHub issueThis original problem was reported in #6338. It affects only fullcalendar version 4.x and 3.x. It was triggered by a change in the way Chrome does table layouts. It only affects calendars that have the slotWidth
option set to a value approximately smaller than 30
. It would prevent certain lines from extending all the way to the edge of the view and would prevent some events from being dragged:
Upgrading via NPM/Yarn (for v4)
If you are using v4.x, you can fix this bug by upgrading the @fullcalendar/timeline
package to 4.4.3
:
npm install '@fullcalendar/timeline@^4.4.3'
Please do this even if you are only using the @fullcalendar/resource-timeline
package. One is a dependency of the other.
Uprading with archives (for v4)
If you’re not using a package manager, you can upgrade to v4.4.3 manually:
Can’t upgrade? Use a CSS fix
If you are using v3.x, or if upgrading is not convenient for you, then you can apply the following CSS manually:
.fc col { min-width: auto !important }
If you apply the CSS manually, and you do NOT have slotWidth
explicitly set, you might need to set it if the slots appear smaller than you expect. Upgrading to v4.4.3 does not have this caveat.
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (3 by maintainers)
Top GitHub Comments
@ajaypatelaj and @amruthraodigital , if you are using angular, the instructions are the same. Make sure you have v4.4.3 of the
@fullcalendar/timeline
plugin by doing this:@goemaere, thanks for reminding me. yes i will. in the next two days. until then, the CSS-only fix will work