Fix #2914 #3412
Merged
Fix #2914 #3412
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
|
I removed my attempt to fix this as well, which didn't seem to have worked on live. |
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.
When XSLT call-template is used and the template includes Javascript (probably anything really) with '=>' it helpfully converts the '>' to the HTML entity '>'. This of course breaks the Javascript when it comes round to running the stuff.
This change uses a different approach to setting up highlight.js that does not need '=>'.
I should have probably worked out why the '>' is being converted to '>' but realistically I know more about Javascript than I do about XSLT and life is short.