Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was testing some settings and edge cases of the PDF printing support using a ~50 slide presentation.
In the Chrome devtools I noticed that the flame chart of a performance recording showed a lot of forced layout spans.
I looked into the areas where this happened and applied the advice to improve time spent on layout:
When building this library with these changes, and testing again with the presentation I was working with, performance improved and there were less forced layout spans in the performance flame graph.
The code should still do the same functionally.
Promises and requestAnimationFrame were already used elsewhere and async/await gets compiled to promises, so browser compatibility should also remain the same.
Thank you for all the work on this library!