🤖 fix: use double RAF in jumpToBottom for reliable scroll position #887
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.
When switching workspaces,
jumpToBottomwas executing synchronously before browser layout was complete. This caused scrolling to land 'almost at the bottom' instead of fully at the bottom.The fix uses double
requestAnimationFrame(matchingperformAutoScroll):scrollHeightafter layoutsetAutoScroll(true)is set immediately to prevent flicker of the 'jump to bottom' button.Generated with
mux