Fix for issue 9018: Javadoc viewer shows HTML comments#9071
Merged
matthiasblaesing merged 1 commit intoapache:masterfrom Dec 6, 2025
Merged
Fix for issue 9018: Javadoc viewer shows HTML comments#9071matthiasblaesing merged 1 commit intoapache:masterfrom
matthiasblaesing merged 1 commit intoapache:masterfrom
Conversation
Signed-off-by: Maksim Khramov <maxtemplaar@gmail.com>
matthiasblaesing
approved these changes
Dec 6, 2025
Contributor
matthiasblaesing
left a comment
There was a problem hiding this comment.
Looks sane to me. Thank you!
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
2 participants
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.
Fix for #9018
Given html tag passed to default section of inlineTags method and thus changes opening bracket convered to 'lt' entity
I add extra case 'COMMENT' to bupass this DocTree tag processing
Add test to check this
^Add meaningful description above
Click to collapse/expand PR instructions
By opening a pull request you confirm that, unless explicitly stated otherwise, the changes -
Please make sure (eg.
git log) that all commits have a valid name and email address for you in the Author field.If you're a first time contributor, see the Contributing guidelines for more information.
If you're a committer, please label the PR before pressing "Create pull request" so that the right test jobs can run.
PR approval and merge checklist:
If this PR targets the delivery branch: don't merge. (full wiki article)