Ensure that cursor state change is always emitted upon restoring state #203451
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.
Fixes #203345
It seems that the distinction between cases where the scrollbar background appears and where it does not lies in whether onCursorStateChanged is called or not. When a file is opened, restoreCursorState fires events that initialize the cursor state, and _emitStateChangedIfNecessary determines whether the
CursorStateChangedEvent
should be fired by comparing the previous and current cursor states. However, it appears that the default value for the cursor position in a newly opened view is (1,1), which results in theCursorStateChangedEvent
not being fired if the cursor position after restoration is also (1,1) – the cursor positioned before the first character on the first line. Without this event, certain parts of DecorationsOverviewRuler do not initialize properly, leading to the problem I linked above.To address this, I've ensured that cursor events are emitted if they were caused by the
restoreState
.