Open felixfbecker opened 6 years ago
To clarify, the fix for this is what I mentioned in https://github.com/sourcegraph/sourcegraph/issues/1341#issuecomment-446302797
Additionally, a theme switcher would help by allowing you to select more arbitrary themes (which would not 'fit in' with the rest of Sourcegraph via a user setting). This is not a fix, but is a related / helpful addition.
@jeanduplessis @Joelkw candidate for the accessibility-related work. wdyt?
Heads up @jeanduplessis @alicjasuska @felixfbecker - the "team/frontend-platform" label was applied to this issue.
Is this still a problem after the redesign?
@pdubroy Yes, the redesign didn't touch the syntax highlighting.
Thanks @felixfbecker, I wasn't sure if we were still using the same theme back in 2018 as we are now.
It's also worth noting that some of these colors don't meet AA standards for contrast ratio:
Thanks to Mojave I got into dark theme again, but I noticed that code is significantly harder to read because it has less color variation in syntax highlighting:
In light theme,
this
is red and the keywords in the parameter types are green. In dark theme, they are all the light blue of the rest of the code. Also, in light theme, control-flow keywords likeif
are green, which is very different from the light blue of the rest of the code. But in dark theme, they are just dark blue, which is a lot less different.Here is the same snippet in VS Code with the Sourcegraph Dark theme:
Note how types are green, and control-flow keywords are purple. This is how the dark theme on Sourcegraph should look like