-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix broken code rendering on macOS Firefox with no local copy of Source Code Pro #9
Comments
This is adobe-fonts/source-code-pro#217, which links through to https://bugzilla.mozilla.org/show_bug.cgi?id=1520157. |
What if we just removed the local() part and relied on serving our own copy? Does it work then? |
I tried playing around with this and got sidetracked by finding a crashing bug in Firefox (https://bugzilla.mozilla.org/show_bug.cgi?id=1649676 if you’re interested). My feeling is no (local is actually allowing the working copy of Source Code Pro) but I’ll dig into this in more detail tonight to double-check |
OK. If it doesn't work at all then we can switch to Fira. Maybe you can put together that pull request if you have some free time. |
The main reason to do this is to fix standardebooks/manual#9, but the font is also about 20% smaller which is a nice benefit. Fira Mono is also licensed under OFL so no change there. I have no stylistic preference either way, but they’re broadly similar in look. Fira Mono has no italic faces, but we have no italic display of source code so no loss there.
The main reason to do this is to fix standardebooks/manual#9, but the font is also about 20% smaller which is a nice benefit. Fira Mono is also licensed under OFL so no change there. I have no stylistic preference either way, but they’re broadly similar in look. Fira Mono has no italic faces, but we have no italic display of source code so no loss there.
Something’s weird with our code display in Firefox on macOS: if you don’t have Source Code Pro installed locally it falls back to just black rendering, regardless of CSS.
I’ll have a dig into why this might be happening.
The text was updated successfully, but these errors were encountered: