fix(desktop): honor user font in UI chrome#3605
Merged
esengine merged 1 commit intoJun 9, 2026
Merged
Conversation
Contributor
Author
|
Small note on the CSS font-family choices: Parent UI containers use |
esengine
approved these changes
Jun 9, 2026
esengine
left a comment
Owner
There was a problem hiding this comment.
Reviewed: this is a genuine bug-fix (not a cosmetic UI change) and CI is green. Approving.
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
3 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.
What
Update desktop UI chrome text to follow the user's selected font family instead of forcing the monospace stack in ordinary interface copy.
This covers visible chrome such as:
Technical text surfaces remain monospace: code, diffs, tool output, file paths, hashes, logs, and other identifier-heavy content.
Why
The Appearance -> Font setting already updates the app's
--sansstack, but several user-facing labels were pinned to--mono, making them visually inconsistent with composer placeholder/input text such as "给 Reasonix 发消息...".Testing
npm.cmd run check:cssnpm.cmd run test:allnpx.cmd tsc --noEmit -p tsconfig.test.jsongit diff --checkNote: I attempted to start the Vite dev server for visual QA, but this Windows environment has duplicate
Path/PATHenvironment entries that caused PowerShell process launching to fail. The CSS and frontend test checks above passed.