Inline code becomes unreadable in VS Code high-contrast themes
Maintainers usually reply within 8 days
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 63/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- css, typescript, vscode
- Domain
- accessibility, frontend
Research direction
Start by locating the Markdown renderer and its inline code styles, then check how those styles behave with VS Code's Dark High Contrast and Light High Contrast themes. Reproduce the black-on-black rendering using an assistant response with an inline identifier such as Math.Clamp. Done means inline code remains readable in both high-contrast themes while standard themes continue to work.
Written by the indexing model from the issue text.
Description
Description
When using the Continue extension for VS Code with the built-in high-contrast color themes, inline code in assistant responses can become unreadable because the text foreground and background colors do not have sufficient contrast.
This occurs with both Dark High Contrast and Light High Contrast. Standard dark and light themes appear to work correctly.
For example, in the following assistant response:
If this is a utility function used frequently in a game engine or math library: Go with the Math.Clamp version (Option 2) if you want it as tight as...
The Math.Clamp identifier is rendered in black against a black background, while the surrounding text is visible.
Steps to reproduce
Open VS Code with the Continue extension installed.
Set the color theme to Dark High Contrast or Light High Contrast.
Ask Continue a question that produces an answer containing inline code identifiers, such as Math.Clamp.
Inspect the rendered assistant response.
Expected behavior
Inline code and identifiers should remain readable in all supported VS Code themes, including both high-contrast themes. Foreground and background colors should be selected together to maintain sufficient contrast.
Actual behavior
Some inline code identifiers are rendered in a foreground color that matches or closely resembles their background, making them difficult or impossible to read.
Possible cause
The issue may be related to the Markdown renderer's CSS for inline code elements. If the renderer overrides the code background without explicitly setting a compatible foreground color, VS Code's high-contrast theme defaults may produce an unreadable combination.
A potential fix would be to use appropriate VS Code theme variables for both foreground and background colors, with accessible fallbacks.
Environment
Operating sy
em: Linux (Fedora)
Editor: Visual Studio Code
Extension: Continue
Affected themes: Dark High Contrast and Light High Contrast
Continue and VS Code versions: Not yet recorded
The issue appears to be specific to high-contrast themes rather than the model generating the response.
- Dominant language
- TypeScript
- Stars
- 36.5k
- Forks
- 5.6k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 continuedev/continue
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
continuedev/continue#13486 ·
Maintainers usually reply within 8 days
-
Chat panel overflows horizontally when VS Code zoom level is increased (Cmd/Ctrl + +)Possibly taken @tang-ontheway claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
continuedev/continue#13483 ·
Maintainers usually reply within 8 days
-
Docs: show tool selection for a shared remote MCP endpointPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
continuedev/continue#13464 · 1 comment ·
Maintainers usually reply within 8 days
-
create_new_file writes a JSON file on one line when the model sends its contents as a JSON valuePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
continuedev/continue#13363 ·
Maintainers usually reply within 8 days
-
Difficulty 1/5 Under an hour Newbie friendliness 66/100
continuedev/continue#13352 ·
Maintainers usually reply within 8 days
All issues in continuedev/continue
Similar issues
-
area-templates triage:bot-seen triage:needs-human
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/aspire#22356 · 1 comment ·
Maintainers usually reply within 1 day
-
Archiving an agent that is not loaded keeps its old updatedAtPossibly taken @luoph claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
content triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
contributor: external needs review severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
JSPrismarine/JSPrismarine#3214 ·
Maintainers usually reply within 1 day