desktop: One Dark Pro workspace messages have low contrast
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- css, typescript
- Domain
- accessibility, frontend
Research direction
Look for theme definitions, likely in a themes directory or CSS variable files. The issue mentions CSS tokens --v2-blue-300, --v2-text-text-contrast, --v2-blue-1200, and --v2-background-bg-accent. Find where these are defined for One Dark Pro, particularly for workspace sessions. Check the contrast ratio and adjust the text or background color to meet accessibility standards. Test the change in both local and workspace sessions.
Written by the indexing model from the issue text.
Description
Description
Summary
With One Dark Pro, user messages are illegible (1.2 to 1 contrast ratio) when in a "workspace session". "local sessions", in contrast, are highly legible (14.1 to 1 contrast ratio). Screenshots below show the difference.
Expected behavior
User messages remain legible in both session types with this theme.
Actual behavior
| One Dark Pro dark | Local | Workspace |
|---|---|---|
| CSS text token | --v2-blue-300 |
--v2-text-text-contrast |
| Sampled text | #d5ebff |
#a8afbc |
| CSS background token | --v2-blue-1200 |
--v2-background-bg-accent |
| Sampled background | #021c31 |
#3eacff |
| Text contrast | 14.1:1 | 1.2:1 |
Plugins
opencode-mystatus
OpenCode version
2.0.6 and 2.0.15
Steps to reproduce
- In the desktop app, choose One Dark Pro and use dark mode.
- Open a session in one of the project's workspace directories, distinct from its main worktree, and view a user message.
- Compare the message with one in a session in the project's main worktree.
Screenshot and/or share link
| Local session | Workspace session |
|---|---|
Operating System
Windows 11 (10.0.26200.0)
Terminal
OpenCode desktop app
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- Avg merge
- 9h 42m
- Merged PRs (30d)
- 389
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from anomalyco/opencode
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
All issues in anomalyco/opencode
Similar issues
-
bug(cli): hapi doctor inline-media prints a fabricated B:\ helper-script path in packaged installs Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Crush Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
catppuccin/catppuccin#3125 ·
-
Add a SECURITY.md Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ElementsProject/cln-application#167 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Quantco/pnpm-licenses#17 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100