Font is always black after installing macOS 11 (Source Code Pro font or derivatives need to be updated) #100840

anukul · 2020-06-23T11:24:35Z

VSCode Version: 1.46.1
OS Version: macOS Big Sur Version 11.0 Beta (20A4299v)

Steps to Reproduce:

Upgrade to macOS 11.0 Developer Beta 1
Open VS Code, switch between the bundled colour themes

Does this issue occur when all extensions are disabled?: Yes

beratgashi · 2020-06-23T11:46:39Z

Same problem here :/

AugustDev · 2020-06-23T14:43:08Z

Same problem, unworkable.

aeschli · 2020-06-24T07:38:46Z

Likely a Electron/Chromium issue...

miguelsolorio · 2020-06-24T19:05:23Z

Not sure if this helps but I also upgraded to Big Sur and don't see this happening (either on Stable or Insiders):

Specs:

adregia · 2020-06-24T20:21:28Z

For what it's worth, the issue subsided for me when I disabled my custom font settings.

With custom font enabled:

Without:

The issue appears to manifest itself with Hasklig in particular. As you can see, Verdana is not problematic (also tried Helvetica):

Although Hasklig is not a pre-installed system font, I also tried Lexend Deca, which is also custom, and presented no issues rendering color. Reinstalling Hasklig did not alleviate the issue.

Scopes inspector indicates the correct foreground color:

miguelsolorio · 2020-06-24T21:31:34Z

@adregia thanks for investigating, can also confirm that using Hasklig breaks syntax highlighting. Other custom fonts like Input Mono seem to work fine though.

alexdima · 2020-06-28T13:48:31Z

@misolori I think this might be an electron/chromium issue. Could you please try the standalone editor in Chrome -- https://microsoft.github.io/monaco-editor/ . You could just edit the font-family on the editor view-lines dom node.

miguelsolorio · 2020-06-29T15:23:54Z

@alexdima also repros on the standalone editor in Chrome:

alexdima · 2020-06-29T20:40:17Z

It looks like this font does not want to be rendered with colors in Big Sur by Chromium.

@misolori Could you please create a simple HTML page and report an issue to Chromium at https://bugs.chromium.org/p/chromium/issues/list

miguelsolorio · 2020-06-29T21:05:35Z

Created https://bugs.chromium.org/p/chromium/issues/detail?id=1100502. Also worth noting that I tested this on Safari, Firefox, and Edge and they all fail to render the text except for Safari.

alexdima · 2020-06-30T20:05:29Z

Thanks a lot @misolori !

jeremyFreeAgent · 2020-08-08T17:43:32Z

I can confirm Hasklig breaks colors. Same issue on Hyper (https://github.com/vercel/hyper/).

zavan · 2020-08-10T10:00:44Z

"editor.fontFamily": "Source Code Pro" breaks it too, same problem. Removing the setting works.

balupton · 2020-08-11T08:58:34Z

Is font ligatures to blame then?

lllyin · 2020-08-31T03:00:06Z

disable the editor.fontFamily. i am working.

madeleineostoja · 2020-09-01T21:49:51Z

This is down to a Source Code Pro rendering bug in chromium. I have no idea why, but anywhere that uses it or it's derivatives, including websites etc, has the same issue.

Changing your font family to any other font will fix it.

falcn · 2020-09-18T14:17:27Z

The issue appears to manifest itself with Hasklig in particular.

For anyone who needs replacement, ligaturized Source Code Pro is the same font as Hasklig, and it works with Big Sur
https://github.com/ToxicFrog/Ligaturizer/

WillBeebe · 2020-09-26T02:06:34Z

Downloading other font families you can easily repo this in OX11

W/ Monoid, it works, without it doesn't. Same w/ Hasklig

"Monoid", "Source Code Pro", sans-serif

leepowelldev · 2020-11-13T10:37:31Z

Is there anything close to Source Code Pro which is known to work?
UPDATE: Just downloaded Source Code Pro again from Google Fonts, and overwrote my existing files, seems to work ok now.

punchcutter · 2020-11-25T05:55:21Z

The latest releases of Source Code Pro and Source Han Code JP have removed the SVG table to make them work as expected on macOS 11.

leepowelldev · 2020-11-25T09:22:33Z

Does anyone using Source Code Pro get a collapse on certain html elements/attributes which end in 'l' and the attribute starts with 'l' ?? Screenshot attached showing how it behaves on <html lang="en"> - it seems to collapse the whitespace and replace it with a dot.

alexdima · 2020-11-25T09:54:25Z

@leepowelldev Yes, I've seen this before. See #106583. The workaround is to use "editor.fontLigatures": "'ccmp' off"

leepowelldev · 2020-11-25T10:58:49Z

@alexdima Thank you so much! You have no idea how much that's been driving me nuts!

arjunguha · 2020-11-30T15:06:38Z

Very helpful. Thanks. I'm using Source Code Pro Version 2.030;PS 1.0;hotconv 16.6.51;makeotf.lib2.5.65220 and MacOS 11.0.1. Setting "editor.fontLigatures": "'ccmp' off" did not work for me.

However, removing 'Source Code Pro' from "editor.fontFamily" resolves the problem.

hidekuro · 2020-12-11T05:25:58Z

Try re-install font to resolve problem.

In my case, I using "Source Han Code JP".
I saw correct colors after re-install the font.

bjesuiter · 2020-12-15T22:13:06Z

For what it's worth, the issue subsided for me when I disabled my custom font settings.

With custom font enabled:

Without:

The issue appears to manifest itself with Hasklig in particular. As you can see, Verdana is not problematic (also tried Helvetica):

Although Hasklig is not a pre-installed system font, I also tried Lexend Deca, which is also custom, and presented no issues rendering color. Reinstalling Hasklig did not alleviate the issue.

Scopes inspector indicates the correct foreground color:

Thanks for your research, this works great!
I normally use 'Source Code Pro' font, but when I delete it from my font settings, the next font will be used.
The next font is 'Menlo' and since it's installed on my system, it loads just fine.

LyonUp · 2020-12-31T01:13:04Z

"editor.fontFamily": "Source Code Pro" breaks it too, same problem. Removing the setting works.

I also solved it by installing the "Source Code Pro" font：https://github.com/adobe-fonts/source-code-pro/releases/tag/variable-fonts

jundl77 · 2021-01-03T01:03:19Z

FYI, the fix for Hasklig is to install version 1.2 or later: https://github.com/i-tu/Hasklig/releases/tag/v1.2

Somesa · 2021-04-17T09:00:56Z

Reinstalling 'Source Code Pro' font from google fonts worked for me
Thanks 👍

guylyons · 2021-05-03T14:46:07Z

Removing my font choice specification in the settings.json fixed it for me.

behemos · 2021-06-01T09:02:11Z

Is there anything close to Source Code Pro which is known to work?
UPDATE: Just downloaded Source Code Pro again from Google Fonts, and overwrote my existing files, seems to work ok now.

👍 https://fonts.google.com/specimen/Source+Code+Pro

blakewatson · 2021-06-10T22:27:01Z

In case some poor soul has the same problem I did... Source Code Pro was all black in VS Code. No highlighting. I tried re-downloading a newer version of Source Code Pro as suggested above but it didn’t work.

After nearly going mad, I realized that I also had Source Code Pro installed via the Adobe Creative Cloud app and that version of the font was the old broken one. VS Code was preferring the Adobe version. After removing that from Adobe CC and re-installing the latest version of Source Code Pro (and reloading the VS Code window) it works perfectly.

dbaeumer assigned aeschli Jun 23, 2020

bpasero added macos-big-sur themes Color theme issues labels Jun 23, 2020

aeschli assigned deepak1556 Jun 24, 2020

aeschli assigned alexdima and unassigned aeschli Jun 26, 2020

alexdima added the font-rendering Font rendering issues label Jun 28, 2020

alexdima added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Jun 29, 2020

bpasero added the upstream-issue-linked This is an upstream issue that has been reported upstream label Jun 30, 2020

This was referenced Nov 13, 2020

SCP cannot be styled in various apps (e.g. Sublime Text, VSCode) on macOS 11 (Big Sur) adobe-fonts/source-code-pro#250

Closed

No color on macOS Big Sur i-tu/Hasklig#123

Closed

goiwai mentioned this issue Nov 25, 2020

The font is always black after upgrading Big Sur adobe-fonts/source-han-code-jp#17

Closed

alexdima changed the title ~~Font is always black after installing macOS 11 (fonts need to be reinstalled)~~ Font is always black after installing macOS 11 (Source Code Pro font or derivatives need to be updated) Nov 25, 2020

patrickserrano mentioned this issue Dec 2, 2020

Dark themes use black text in editor window on MacOS 11 microsoft/azuredatastudio#13549

Closed

gjsjohnmurray mentioned this issue Dec 3, 2020

The code part can't show perfect, the code is black, there is not any other color; #111782

Closed

Tehnix mentioned this issue Jan 3, 2021

Update Hasklig to v1.2 ryanoasis/nerd-fonts#555

Merged

5 tasks

jorgebucaran mentioned this issue Jan 20, 2021

Black foreground color + No syntax highlighting porsager/flems#93

Closed

IllusionMH mentioned this issue Feb 8, 2021

Restarting no longer fixing the issue. No extensions installed, settings are seldom changed except for theme. All dark themes have this issue #116057

Closed

jorgebucaran mentioned this issue Feb 15, 2021

fish_config does not work in MacOS 11.2 Chrome or Firefox fish-shell/fish-shell#7714

Closed

sorens mentioned this issue Mar 10, 2021

Dark Mode Too Far! adobe-fonts/source-code-pro#267

Closed

heussd added a commit to heussd/dotfiles that referenced this issue Apr 29, 2021

Temporary workaround for Code bug microsoft/vscode#100840

15b317d

FraBle mentioned this issue May 26, 2021

Fix incorrect file permissions google/fonts#3343

Merged

anukul closed this as completed Jun 2, 2021

IllusionMH mentioned this issue Jun 22, 2021

all colors are just washed away and no highlighting #126931

Closed

IllusionMH mentioned this issue Jul 1, 2021

All code is black; color themes not working. #127696

Closed

IllusionMH mentioned this issue Jul 10, 2021

Using a custom font (source code pro) disables syntax highlighting of C++ #128380

Closed

deepak1556 mentioned this issue Jul 17, 2021

VSCode doesn't render variable font weights below 400 in Big Sur #128769

Closed

github-actions bot locked and limited conversation to collaborators Jul 17, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Font is always black after installing macOS 11 (Source Code Pro font or derivatives need to be updated) #100840

Font is always black after installing macOS 11 (Source Code Pro font or derivatives need to be updated) #100840

anukul commented Jun 23, 2020 •

edited

Loading

beratgashi commented Jun 23, 2020

AugustDev commented Jun 23, 2020

aeschli commented Jun 24, 2020

miguelsolorio commented Jun 24, 2020 •

edited

Loading

adregia commented Jun 24, 2020

miguelsolorio commented Jun 24, 2020

alexdima commented Jun 28, 2020

miguelsolorio commented Jun 29, 2020

alexdima commented Jun 29, 2020

miguelsolorio commented Jun 29, 2020

alexdima commented Jun 30, 2020

jeremyFreeAgent commented Aug 8, 2020

zavan commented Aug 10, 2020

balupton commented Aug 11, 2020

lllyin commented Aug 31, 2020

madeleineostoja commented Sep 1, 2020 •

edited

Loading

falcn commented Sep 18, 2020 •

edited

Loading

WillBeebe commented Sep 26, 2020

leepowelldev commented Nov 13, 2020 •

edited

Loading

punchcutter commented Nov 25, 2020

leepowelldev commented Nov 25, 2020 •

edited

Loading

alexdima commented Nov 25, 2020

leepowelldev commented Nov 25, 2020

arjunguha commented Nov 30, 2020

hidekuro commented Dec 11, 2020

bjesuiter commented Dec 15, 2020

LyonUp commented Dec 31, 2020

jundl77 commented Jan 3, 2021 •

edited

Loading

Somesa commented Apr 17, 2021

guylyons commented May 3, 2021

behemos commented Jun 1, 2021

blakewatson commented Jun 10, 2021

Font is always black after installing macOS 11 (Source Code Pro font or derivatives need to be updated) #100840

Font is always black after installing macOS 11 (Source Code Pro font or derivatives need to be updated) #100840

Comments

anukul commented Jun 23, 2020 • edited Loading

beratgashi commented Jun 23, 2020

AugustDev commented Jun 23, 2020

aeschli commented Jun 24, 2020

miguelsolorio commented Jun 24, 2020 • edited Loading

adregia commented Jun 24, 2020

miguelsolorio commented Jun 24, 2020

alexdima commented Jun 28, 2020

miguelsolorio commented Jun 29, 2020

alexdima commented Jun 29, 2020

miguelsolorio commented Jun 29, 2020

alexdima commented Jun 30, 2020

jeremyFreeAgent commented Aug 8, 2020

zavan commented Aug 10, 2020

balupton commented Aug 11, 2020

lllyin commented Aug 31, 2020

madeleineostoja commented Sep 1, 2020 • edited Loading

falcn commented Sep 18, 2020 • edited Loading

WillBeebe commented Sep 26, 2020

leepowelldev commented Nov 13, 2020 • edited Loading

punchcutter commented Nov 25, 2020

leepowelldev commented Nov 25, 2020 • edited Loading

alexdima commented Nov 25, 2020

leepowelldev commented Nov 25, 2020

arjunguha commented Nov 30, 2020

hidekuro commented Dec 11, 2020

bjesuiter commented Dec 15, 2020

LyonUp commented Dec 31, 2020

jundl77 commented Jan 3, 2021 • edited Loading

Somesa commented Apr 17, 2021

guylyons commented May 3, 2021

behemos commented Jun 1, 2021

blakewatson commented Jun 10, 2021

anukul commented Jun 23, 2020 •

edited

Loading

miguelsolorio commented Jun 24, 2020 •

edited

Loading

madeleineostoja commented Sep 1, 2020 •

edited

Loading

falcn commented Sep 18, 2020 •

edited

Loading

leepowelldev commented Nov 13, 2020 •

edited

Loading

leepowelldev commented Nov 25, 2020 •

edited

Loading

jundl77 commented Jan 3, 2021 •

edited

Loading