Repository navigation
Fix Markdown preview layouts and misleading change highlights - #28
Merged
Merged
Conversation
rcosteira79
marked this pull request as ready for review
October 29, 2026 19:28
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
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.
Markdown previews ignored Split/Unified and always rendered two columns. Both Shiki and Monaco now follow the selected layout, including changes made while a preview is open. Unified interleaves additions and removals using captured source lines, keeps unchanged blocks and list items once, and preserves complete tables and code fences.
Preview highlighting now applies to the changed list item or table row instead of coloring the whole container. Wrapped list-item text stays with its item. The comparison-range menu also opens when no checkpoint exists and explains why “Since last review” is unavailable; it becomes selectable after saving a checkpoint.
Validation: 107 related tests, type checking, JavaScript syntax checks, and a focused Chromium regression covering both renderers, repeated layout switches, accurate list highlights, added/emptied files, and checkpoint range switching. The browser regression is included in the existing Monaco CI suite. Docker was not used.