When searching, the highlighted text can become unreadable if it is a comment.

[shoulders]

Version: 1.107.0 (user setup)
Commit: 618725e67565b290ba4da6fe2d29f8fa1d4e3622
Date: 2025-12-10T07:43:47.883Z
Electron: 39.2.3
ElectronBuildId: 12895514
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26100

Dracula Theme Official: 2.25.1
Variant: Dracula Theme Soft

Language used in example: PHP
Font: Fira Code

When searching and highlighting there are scenarios where I cannot read the text, in particular for me it is when the text being searched for is a comment.

Below I have gone through some easy to follow steps to outline the issue.

Tanks

Step 1) Normal Text Highlight

Just text selected with the mouse

Step 2) I now do a page search

I now do a page search for as you cannot really delete

In the image below you can see 3 areas and3 different colours. delete is almost unreadable.

• information and set blocked = part of the original text highlight but not part of the page search
• as you cannot really = part of the original text highlight and now highlighted by the page search
• delete = NOT part of the original text highlight and now highlighted by the page search

Step 3) I now do a project search

I now do a page search for cannot really delete and of course the page search is still enabled from above.

There appears to be 2 different colour variants of the search highlighting here, but I am not sure why.

both the grey (as you)and orange are readable (cannot really delete) but I would say the orange looks like it has been greyed a little.

The first part is a murky orange and cannot be read (as you), the next section is a vibrant orange and is easily read (cannot really delete)

Step 4) Page search only

This is a page search only for as you cannot really delete. As you can see the text is not readable.

Step 5) Project search only

This is a project search only for as you cannot really delete. As you can see the text is not readable.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

🔗 Similar Issues

Related Issues

• Comments and strings barely visible notepad-plus-plus#65
• Warning PeakViewColor readability issue #279
• 🐞 Dracula Pro - lack of contrast in Firefox address bar when selecting text dracula-theme#1037
• [Bug/Enhancement] No highlight when selecting snippet placeholder #281

👤 Suggested Assignees

• OwenGrumbles
• Kwaadpepper
• helgatheviking
• imhuay

---

🧪 Issue enrichment is currently in early access.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

[shoulders]

visual-studio-code/src/dracula.yml

Line 197 in 7abb205

editor.findMatchBackground: !alpha [ *ORANGE, 80 ]

I used the following options throught my settings.json to override this for now

• "editor.findMatchBackground": "#FFB86C50" same orange but at 50 percent opacity and is much easier to read than the original 80%
• "editor.findMatchBackground": "#00800050" this is a nice green and easy to read ( 50 percent opacity )

Additional

• This is a guide for you guys to look at, the final colour decision are up to you 😄
• There is no comment for this setting in the template file. it should be:
  editor.findMatchBackground: !alpha [ *ORANGE, 80 ] # Color of the current search match.
• Maybe the token colour needs overriding for a search hit.