Repository navigation
Fix double escaping in fenced code previews - #188
Merged
jaywcjlove merged 1 commit intoNov 4, 2026
Merged
Conversation
jaywcjlove
added a commit
that referenced
this pull request
Nov 4, 2026
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.
Problem
Markdown fenced HTML such as
<div />is displayed as<div />in the highlighted preview because its contents are escaped twice. Fixes #177.Change
Escape the source once before parsing the preview. Add regression coverage for fenced HTML and JavaScript, literal entities, and markup escaping with and without the highlighting plugin.
Validation
AI assistance: Codex assisted with investigation, implementation and validation.