nhcarrigan/hikari-desktop
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 9 Pull Requests 36 Actions Releases 22 Activity

feat: allow users to specify a custom font #176

New Issue
Closed
opened 2026-03-03 15:50:16 -08:00 by hikari · 0 comments
hikari commented 2026-03-03 15:50:16 -08:00
Owner
Copy Link
Copy Source

Summary

Allow users to personalise the app's typography by specifying a custom font, either from a local file path or a remote URL (e.g. Google Fonts).

Motivation

The current font is fixed. Users with strong font preferences — or accessibility needs that are better served by a particular typeface — have no way to change it.

Proposed Behaviour

  • Add a Custom Font field to the Settings/Appearance section
  • Accept two input formats:
    • Local file path — e.g. /home/user/.fonts/MyFont.ttf or C:\Windows\Fonts\MyFont.ttf; load via Tauri's filesystem API and inject as a @font-face rule
    • Remote URL — e.g. a Google Fonts @import URL or a direct .woff2 link; inject as a <link> or @import in the app's CSS
  • Persist the setting in the existing config (new custom_font field on the Rust Config struct and the frontend configStore)
  • Apply the font to the terminal/chat area at minimum; ideally to the whole UI
  • Provide a Reset to default button to clear the custom font
  • Validate the URL/path before saving and show an inline error if it is malformed

Acceptance Criteria

  • New custom_font: Option<String> field on the Rust Config struct
  • Config migration handles missing field gracefully (defaults to None)
  • Frontend configStore exposes customFont and setCustomFont()
  • Settings UI has a text input for the font value with local/URL toggle or auto-detection
  • Font is applied dynamically when the setting changes (no restart required)
  • Reset to default clears the field and restores the original font
  • Invalid paths/URLs surface a user-visible error
  • Tests cover the new config field and store methods

Notes

  • For local files, consider using a CSS @font-face with a blob: URL created from the file's binary content, so it works cross-platform without filesystem restrictions
  • For remote URLs, simply injecting a <link rel="stylesheet"> or a CSS @import should suffice — no Tauri invoke needed

✨ This issue was created with help from Hikari~ 🌸

## Summary Allow users to personalise the app's typography by specifying a custom font, either from a local file path or a remote URL (e.g. Google Fonts). ## Motivation The current font is fixed. Users with strong font preferences — or accessibility needs that are better served by a particular typeface — have no way to change it. ## Proposed Behaviour - Add a **Custom Font** field to the Settings/Appearance section - Accept two input formats: - **Local file path** — e.g. `/home/user/.fonts/MyFont.ttf` or `C:\Windows\Fonts\MyFont.ttf`; load via Tauri's filesystem API and inject as a `@font-face` rule - **Remote URL** — e.g. a Google Fonts `@import` URL or a direct `.woff2` link; inject as a `<link>` or `@import` in the app's CSS - Persist the setting in the existing config (new `custom_font` field on the Rust `Config` struct and the frontend `configStore`) - Apply the font to the terminal/chat area at minimum; ideally to the whole UI - Provide a **Reset to default** button to clear the custom font - Validate the URL/path before saving and show an inline error if it is malformed ## Acceptance Criteria - [ ] New `custom_font: Option<String>` field on the Rust `Config` struct - [ ] Config migration handles missing field gracefully (defaults to `None`) - [ ] Frontend `configStore` exposes `customFont` and `setCustomFont()` - [ ] Settings UI has a text input for the font value with local/URL toggle or auto-detection - [ ] Font is applied dynamically when the setting changes (no restart required) - [ ] Reset to default clears the field and restores the original font - [ ] Invalid paths/URLs surface a user-visible error - [ ] Tests cover the new config field and store methods ## Notes - For local files, consider using a CSS `@font-face` with a `blob:` URL created from the file's binary content, so it works cross-platform without filesystem restrictions - For remote URLs, simply injecting a `<link rel="stylesheet">` or a CSS `@import` should suffice — no Tauri invoke needed ✨ This issue was created with help from Hikari~ 🌸
naomi closed this issue 2026-03-03 20:21:58 -08:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/hikari-desktop#176
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?