Fix list.focusPageUp movement with workbench.tree.enableStickyScroll
#202361
+7
−6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
isidorn
approved these changes
Jan 12, 2024
|
Sorry if my review auto-merged the issue and you wanted explicit @joaomoreno review. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR addresses the issue where
list.focusPageUpwas moving up by only one element sometimes whenworkbench.tree.enableStickyScrollwas enabled. The fix involves adjusting the scroll top calculation to account for the sticky scroll height (paddingTop).This is a similar fix to how we solved reveal() with stickyscroll
Fixes #202288