Table: Update of Scroll Width in the next macrotask #1629
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 measured the performance of our project website. And the longest task contained recalculation of scrollbar width. And it was one of the causes why this rerendering macro-task took > 100ms.
So I thought - scrollbar width it's something that we can update in the next macrotask - it should not cause any bugs.
This PR is about moving of recalculation of scrollbar width to future macrotask.