Theme Rendering Changes in v1.0.0 (e.g. Monokai)

[Kcko]

I’m using the Flatlang Monokai theme (reference: https://is.gd/IUW98a), but after a recent update, the syntax highlighting has changed significantly.

Problems I’m experiencing:

• All code appears dimmed/less vibrant
• PHP keywords are no longer bold
• Overall visual contrast and readability has decreased

Here’s a screenshot showing the current appearance: http://remotefiles.rjwebdesign.cz/i/20250605-094852.png

This issue is affecting multiple users - my colleague is experiencing the same problem. Has anyone else encountered this, and is there a known fix or workaround?

Another look from VisualStudio (same theme, only difference is another background, but it does not matter, but colors are more contrast and keywords are more bolder … → https://is.gd/kCia7u)

[imichall]

Hi there, i agree. After update to this version

Version: 1.0.0 (user setup)
VSCode Version: 1.96.2
Commit: 53b99ce608cba35127ae3a050c1738a959750860
Date: 2025-06-04T19:44:25.253Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

I noticed that the colors have faded somehow. Until the previous update, the colors were more contrasting.

[Kcko]

DIFF:

https://is.gd/KZ4CLp vs https://is.gd/nnpTyS

[Kcko]

Contrast ratio contract ratio is incomprehensibly low for keywords, where to set it? Total nonsense.

Short video: https://is.gd/3IQMtO

[Kcko]

“SOLVED” => partially, with this settings (but fking workaround…which is not enough)

    "editor.tokenColorCustomizations": {
        "textMateRules": [
            {
                "scope": ["punctuation.definition.variable.php", "variable.scss", "variable.other.latte"],
                "settings": {
                    "foreground": "#F92670"
                }
            },
            {
                "scope": ["keyword"],
                "settings": {
                    "fontStyle": "bold"
                }
            },
            {
                "scope": ["keyword", "storage.modifier.php", "storage"],
                "settings": {
                    "fontStyle": "bold"
                }
            }
        ]
    },

[sirianni (Eric Sirianni)]

+1 the built-in monokai theme looks less vibrant and the font for some colors/keywords now looks thinner and more difficult to read compared to the same rendering in VS Code.

[imichall]

Hi there, what OS do you use? Im on macos and the colors looks at the same like update before. I`ve had problem on windows only at work.

Both of them are from macos latest version.

and here is basic monokai

[Kcko]

another solution is to set the font boldness to 500 or higher, but that’s just a workaround again.

The contrast is normal on VSC, but not in Cursor.

All my screenshots are from Win 11, can someone from the DEV team comment on this? It’s impossible to watch.

[sirianni (Eric Sirianni)]

I’m using Windows also. It’s fine on VS Code and with older versions of Cursor.

[sirianni (Eric Sirianni)]

@Kcko

another solution is to set the font boldness to 500 or higher

Yes, but this makes the other items too thick.

[InfImpDrive (Infinite Improbability Drive)]

I am a user of the Monokai theme, but not the Flatlang version.

The non-Flatlang Monokai theme works fine it seems; in case you’re not ■■■■ bent on the Flatlang features.

[sirianni (Eric Sirianni)]

@InfImpDrive

The non-Flatlang Monokai theme works fine it seems;

I don’t think this is accurate. I’m using the built-in Monokai theme and I still see this regression.

[Kcko]

So … you have same problem like me and others on Windows?

[Kcko]

yes, but it’s probably better than nothing, but it’s really hard to watch, my eyes hurt and I’m tired of working, what happened?

[sirianni (Eric Sirianni)]

@Kcko how did you come up with those textMateRules?

The "scope":["keyword"] workaround works great for source code (python, etc.) but I’m still seeing the thin font in YAML. What would be the correct way to target YAML keys?

[Kcko]

Hi, it is just workaround, similar to font-weight, but let me show you.
You need turn of inspect scopes via Developer: Inspect …

and then you will see what you need to set if you click on any keyword in your programming language.

Short video: https://is.gd/MVqo2b

(Im maniac and i require “$” with another color ten rest of variable :-)) so i learned to work with mates scopes …)

[sirianni (Eric Sirianni)]

Using this seems to fix both language keywords and YAML keys

    "editor.tokenColorCustomizations": {
        "textMateRules": [
            {
                "scope": [
                    "keyword",
                    "entity.name.tag"
                ],
                "settings": {
                    "fontStyle": "bold"
                }
            }
        ]
    }

[Kcko]

I still see it as a temporary solution (and that’s also because it just simulates sharpness and legibility (it’s definitely not the same)) and it bothers me that the DEV team won’t comment on it.

When I turn on the VSC, this problem is not there.

[sirianni (Eric Sirianni)]

@Kcko

it bothers me that the DEV team won’t comment on it.

My company has an enterprise subscription to Cursor and I created a support request through those channels. Unfortunately, no response after several days.

[Kcko]

truly terrible behavior