Skip to content

Table: Update of Scroll Width in the next macrotask - #1629

Closed
whiteand wants to merge 1 commit into
bvaughn:masterfrom
whiteand:master
Closed

whiteand wants to merge 1 commit into
bvaughn:masterfrom
whiteand:master

Conversation

@whiteand

@whiteand whiteand commented Jan 16, 2021 •

Copy link
Copy Markdown

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.

… It will cause less time spent in the current macrotask
@github-actions github-actions Bot added the Stale label Sep 2, 2024
@github-actions github-actions Bot closed this Sep 2, 2024
@bvaughn

bvaughn commented Oct 18, 2026

Copy link
Copy Markdown
Owner

Sorry for the very long delay in getting back to you about this!

I've just finished a large update for version 10 of react-virtualized (#1900): the library has been rewritten in TypeScript, every component is now a function component (React 18+ is required), and the source moved from source/ to lib/. Because of that, this PR can't be merged as-is. Version 10's Table still measures its scrollbar width (a forced layout) after every render.

If you're still interested in this change, I'd welcome a new PR with it rebased onto the version-10 branch (or onto master once version 10 has been merged).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants