Chrome Refused to load the font '<URL>'

[scottgrobinson]

Everything appears to be working font wise, but chrome dev console throwing this.... sending over your way just incase it hasn't been spotted already and causing issues for anyone else. 120 of these are shown.

Code - OSS
Version: 1.43.0
Commit: 87ebf03
Date: 2020-03-27T19:18:37.387Z
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36

(120) Refused to load the font '<URL>' because it violates the following Content Security Policy directive: "font-src 'self'".

Refused to load the font 'data:font/woff;base64,d09GRgABAAAAAGVUABEAAAAAxuQAAQABAAAAAAAAAAAAAAAAAAAAAAAAAABHREVGAAABgAAAAC4AAAA0ArgC7UdQT1MAAAGwAAAQ6AAALgxKsqRTR1NVQgAAEpgAAAH3AAAELqI5y+RPUy8yAAAUkAAAAE8AAABgaGyBu2NtYXAAABTgAAABlAAAAkQkRATXY3Z0IAAAFnQAAABeAAAAugDsQf1mcGdtAAAW1AAABZcAAAvNb3/BHGdhc3AAABxsAAAACAAAAAgAAAAQZ2x5ZgAAHHQAAEApAAB3CtbiupxoZWFkAABcoAAAADYAAAA2BkubWWhoZWEAAFzYAAAAIAAAACQHFARfaG10eAAAXPgAAAI6AAAEEk4TN4Nsb2NhAABfNAAAAhIAAAISiLhpam1heHAAAGFIAAAAIAAAACACigzgbmFtZQAAYWgAAACUAAABHhQGLdJwb3N0AABh/AAAAq4AAASRk5y6n3ByZ...QxUajCCFt4p9HP4fzdSWs2XhWl5HvJazrIrFUyB0l5dpqcW10lV2wukjMLuAvyMHNiYpgPsrCVXZDKrkpll6UWkh7kABVAFVCDe7UFmxagDegA+hLHRPbqtMo7ZHCpKdT6tPGXybzo0+RXBLoPZt1tELcXxCmAAyZwYTJvdDFZKnDER44X2451rDqCyunIsRWvLSx6wnWqwPj/uX5/KuEy6DL0z6A/Fn79VihxMFJsrlAFy4DpZOcvNlMeNp+BRDLj0r+XFdRxdSNSNxiI/AL3ojKdAAB4AWPw3sFwIihiIyNjX+QGxp0cDBwMyQUbGdictkUwWDAwsDJogTgOPN4c9iz6bMos4iysHFChUDZXJnMWTSZZJrAQt9M+YQYBBh4GTgY2kEZOoJiA0z4GBxiEiDEzuGxUYewIjNjg0BGxkTnFZaMaiLeLo4GBkcWhIzkkAqQkEggceHw5HFkM2VRZJFlYebR2MP5v3cDSu5GJwWUDW9xG1hQXAFAmKZU=' because it violates the following Content Security Policy directive: "font-src 'self'".

(anonymous) @ canIUse.ts:22
t._invokeFactory @ loader.js:1040
t.complete @ loader.js:1050
s._onModuleComplete @ loader.js:1667
s._resolve @ loader.js:1627
s.defineModule @ loader.js:1278
r @ loader.js:1717
(anonymous) @ platform.ts:222
(anonymous) @ fake:1

[code-asher]

We might want to allow data: in the content security policy but I'm not sure. So far I've only seen this caused by browser extensions.

[kylecarbs]

@code-asher is there a negative to us supporting data:?

[code-asher]

I can't think of any negatives. At first it felt odd to me to let browser extensions modify how VS Code looks, but that might actually be a feature.

[kylecarbs]

Closing in favor of #1530