Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Prevent layout trashing in event (un)rendering
See original GitHub issueThis is technically also an issue in FullCalendar, but it’s more noticeably in the scheduler due to the larger number of elements (it is mentioned in this issue)
When the number of events increase, the time it takes to (un)render these events also greatly increases. One of the big factors in this is the recalculation of the layout (This is called layout trashing) as can be seen in this image. (removeEvents called on 2238 events takes 1107ms and takes 344ms of layout recalculations)
One way to possibly prevent this is to use something like fastdom, which batches dom reads and writes as is explained here.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@MartijnWelker, this is most likely much better in v5, though I have not verified
we could potential hardcode the inline/relative concepts, or make them settings that the caller can “hardcode”