Add left-right panel scroll sync in markdown edit/preview mode #166
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
devleejb
deleted the
140-sync-vertical-scrolling-between-markdown-editor-and-viewer-2
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it:
This PR implements a left-right panel scroll sync feature in markdown edit/preview mode. The purpose is to ensure that when scrolling in one panel, the other panel synchronizes to maintain a consistent view for the user.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Currently, when editing or previewing markdown text in CodePair, users need to manually adjust the scroll position in both the edit and preview panels. This can be inconvenient and disrupt the flow of reviewing or writing markdown content. By introducing the scroll sync feature, we aim to improve the user experience by automatically synchronizing the scroll positions of both panels.
Does this PR introduce a user-facing change?:
Additional documentation:
Checklist: