brightBlack and black color values from Solarized Dark Color Scheme are swapped #14684
Labels
Issue-Bug
It either shouldn't be doing this or needs an investigation.
Needs-Triage
It's a new issue that the core contributor team needs to triage at the next triage meeting
Resolution-By-Design
It's supposed to be this way. Sometimes for compatibility reasons.
Windows Terminal version
1.15.3465.0
Windows build number
No response
Other Software
VSCode 1.74.2 with Solarized Dark Color Theme selected
vim 8.1.2262 (inside WSL2)
colortest-256
Steps to reproduce
According to the colors table in https://en.wikipedia.org/wiki/Solarized
the Solarized Dark Color Scheme default values should be
black = #073642
brBlack = #002b36
In VSCode Terminal running in WSL2: Ubuntu-20.04 the color schema seems to be correct. But running the same WSL2 Distro but this time in Windows Terminal, the black and brBlack colors are swapped.
You can visually confirm this by running the colortest-256 test application on both environments:
VSCode Terminal:

Windows Terminal:

Expected Behavior
Both VSCode and Windows Terminal should be able to reproduce the same colors when selecting the same Color Theme/Schema (In this case, Solarized Dark).
I know this can be easily solved at "user configuration" level, but it would be better to have the correct values by default.
Actual Behavior
By using vim, the color swap effect is more noticeable
VSCode Terminal

Windows Terminal

The text was updated successfully, but these errors were encountered: