Repository navigation
fix: re-highlight Prism code blocks after a language toggle - #12
Merged
Merged
Conversation
Three example snippets carry both a Prism language class and data-i18n-html on the same <code> element. Swapping the translation overwrote Prism's highlighted markup with plain text, and nothing re-triggered highlighting since Prism only runs its automatic pass once on page load. Now re-highlights just the affected blocks right after their translated content is set.
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.
Summary
data-i18n-htmlon the same<code>element.docs/js/i18n.jsnow callsPrism.highlightElement()on any affected code block right after its translated content is set.Test plan
node --check docs/js/i18n.jspasses