Guard against null coordsAtPos in VerticalLines - #602
Open
c-tonneslan wants to merge 1 commit into
Open
Conversation
coordsAtPos() returns null when a position is temporarily outside the rendered viewport (scroll, fold, tab switch), causing a TypeError reading coords.left. Skip the pass and let the next recalculation redraw it. Fixes vslinko#601. Signed-off-by: Charlie Tonneslan <cst0520@gmail.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 #601.
VerticalLinesPluginValue.recursive()callsthis.view.coordsAtPos(fromOffset, 1)and immediately readscoords.left/coords.right. CodeMirror'scoordsAtPos()returnsnullwhen a position is temporarily outside the rendered viewport (during scroll, fold, tab switch, or remeasure), producingUncaught TypeError: Cannot read properties of null (reading 'left').This adds a null guard right after the call — matching the fix suggested in the issue. The skipped segment is redrawn on the next scheduled recalculation, so there is no visible regression.
tsc --noEmitpasses.