fix: decode commenter names in comments widget - #507
Merged
AllTerrainDeveloper merged 2 commits intoAug 6, 2026
Merged
Conversation
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.
Closes #496
Description
This PR fixes a visual bug where HTML entities in commenter names (such as ampersands
&) were rendered raw inside the Recent Comments widget on the desktop.Root Causes & Fixes
Missing Entity Decoding in Commenter Name Render:
author_namepayload (e.g.Q&A Guest). The Recent Comments widget set these directly using.textContent, which caused them to render literally on the screen and broke the initials-based avatar bubble generation (grabbing&instead of the correct letter).decodeHTMLutility fromsrc/utils.tsbefore setting it to the author element and generating the avatar initial.Verification
npm run buildcompleted successfully.npm run typecheckcompleted successfully with zero errors.npm run lintcompleted successfully with zero errors.npm run test:jscompleted successfully with all 3789/3789 Vitest tests passing.Before fix
After fix