feat(ui): Source CashSans-Bold and improve overall text rendering #3091
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
- Defines Cash Sans Bold (700 weight) via @font-face, completing the set of Regular, Medium, and Bold weights for Cash Sans. - Applies global font smoothing (`-webkit-font-smoothing: antialiased`) and legibility optimizations (`text-rendering: optimizeLegibility`) to the body element for crisper, clearer text presentation.
loganmoseley
force-pushed
the
blurry-bold-text
branch
from
4f90745 to
b4dee9c
Compare
Contributor
Author
|
@zanesq I’ve rebased on the latest block/goose/main. I have not taken new screenshots. |
lifeizhou-ap
added a commit
that referenced
this pull request
Jul 22, 2025
* main: (32 commits) fix: use sequential when sub recipe task is 1. (#3573) fix: track message id to keep like with like (#3572) Replace mcp_core::prompt with rmcp::model types (#3561) feat (ui): close recipe modals with esc key (#3568) feat: recipes can retry with success criteria (#3474) Env var to set Ollama request timeout (#3516) Updating docs to match new UI (#3552) Improve Claude Code provider error message for missing CLI (#3363) feat: Work around Gemini API tool call quirks (#3328) feat(ui): Source CashSans-Bold and improve overall text rendering (#3091) refactor: Use openapi for recipe endpoint types and in frontend (#3548) Fix Google Analytics error for local dev (#3544) Extension Library Improvements (#3541) fix(ui): enable selection of zero-config providers in desktop GUI (#3378) refactor: Renames recipe route to recipes to be consistent (#3540) Blog: Orchestrating 6 Subagents to Build a Collaborative API Playground (#3528) Catch json errors a little better (#3437) Rust debug (#3510) refactor: Centralise deeplink encode and decode into server (#3489) feat: deprecate jetbrains extension in favor of public one (#2589) ...
michaelneale
added a commit
that referenced
this pull request
Jul 22, 2025
* main: fix: use sequential when sub recipe task is 1. (#3573) fix: track message id to keep like with like (#3572) Replace mcp_core::prompt with rmcp::model types (#3561) feat (ui): close recipe modals with esc key (#3568) feat: recipes can retry with success criteria (#3474) Env var to set Ollama request timeout (#3516) Updating docs to match new UI (#3552) Improve Claude Code provider error message for missing CLI (#3363) feat: Work around Gemini API tool call quirks (#3328) feat(ui): Source CashSans-Bold and improve overall text rendering (#3091) refactor: Use openapi for recipe endpoint types and in frontend (#3548) Fix Google Analytics error for local dev (#3544)
atarantino
pushed a commit
to atarantino/goose
that referenced
this pull request
Aug 5, 2025
…ock#3091) Signed-off-by: Adam Tarantino <[email protected]>
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.
Problem
Previously, text (especially bolded text) could appear blurry. Goose told me that was likely due to a combination of default rendering settings and the potential for “faux bolding” when a true bold font weight was not available.
Changes Implemented
Added
@font-facefor Cash Sans BoldCashSans-Bold.woffandCashSans-Bold.woff2font files. This makes a true bold variant of the Cash Sans font family available to Goose.app.Enhanced Global Text Rendering
bodyelement inmain.css:-webkit-font-smoothing: antialiased;: Improves font sharpness and clarity on macOS by enabling grayscale antialiasing.text-rendering: optimizeLegibility;: Instructs the browser to prioritize legibility, enabling features like kerning and ligatures for a more refined text appearance.All text should now look crisper and easier to read, especially bold text.
Open Question
What combination of these settings do Goose designers prefer? I’ve added both, but we could instead take either one (or neither and close the PR). See Demos for combinations.
Demos
Click the images to open in a new tab, so you can zoom to 100% and not get resizing blurriness.
Before
Choices
original: no -Bold and NOT antialiased
CashSans-Bold antialiased 👈🏼 This is what I’m proposing.
antialiased, no -Bold
CashSans-Bold NOT antialiased