It used to highlight Lisp strings with a brown font. No longer, it seems?

<!-- language: lang-el -->

It still works with IE (11), but it no longer works with Google Chrome (version 49.0.2623.112 m or version 50.0.2661.87 m)

enter image description here

| |

<!-- language: lang-el --> works for me. Note that the spacing is significant.

For more information about syntax highlighting, see the FAQ on the main meta.

By works, I mean that the strings, keywords, etc. are displayed in a different color. However, I agree that the colors are hard to see, especially the string color. In Chrome, I see that strings are in <span class="str"> and that this class has the attributecolor: #4a1c21`. On both Chrome and Firefox on Ubuntu 14.04, with antialiasing on the gray background of code blocks, I can barely distinguish that color from black.

magnified screenshot

"You nee is in #4a1c21 string (str) color, nt-prefi is in #181a1c default (pln) color, but I can barely distinguish those colors. I don't know if the culprit is the choice of colors by Stack Exchange, something inherited from Google Prettify, a problem in Chrome (probably not since Firefox produces visually indistinguishable output), a problem in Linux's antialiasing (but why wouldn't it have shown up earlier?), or a bad interaction between two or more of these.

Following a similar report on Meta Stack Overflow, the colors have now been changed. There's plenty of contrast now (at least if you aren't colorblind).

post-update screenshot

| |
  • It does not work for me (but it used to). (And I had the space after the colon originally. I tried removing it, to see if that would make a difference, but it did not.) – Drew Apr 24 '16 at 14:10
  • @Drew Working for me on emacs.stackexchange.com/questions/21797/… with Chrome 49.0.2623.110. Strange. – Gilles 'SO- stop being evil' Apr 24 '16 at 16:44
  • Does not work for me. I checked with two different monitors, to be sure that wasn't the problem. I reported it to Google. – Drew Apr 25 '16 at 14:51
  • But perhaps the problem is only that there is very little difference between the colors now (?). Adding a screenshot here. – Drew Apr 25 '16 at 14:56
  • @Drew The colors are present in your screenshot, but they're difficult to see, especially the string color looks almost black. This seems to be a combination of the color choice (#4a1c21) and antialiasing seems to make it particularly bad. This isn't just in Chrome, I'm getting the same antialiasing in Firefox. I don't think the colors used to be that muted, and I haven't upgraded my machines recently, so this must be an SE change. – Gilles 'SO- stop being evil' Apr 25 '16 at 16:17
  • Yes, that's what my last comment was saying. Thanks for confirming this. The colors seem to be more muted now - more similar to black. – Drew Apr 25 '16 at 16:57

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .