-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
rustdoc: strange font rendering issue #60365
Comments
A quick fix would be to revert the Source Code Pro update, the Source Serif Pro one is the only important one. I'd like to keep our fonts up to date though. But it looks like either the font or the OS stack is buggy here, and we should investigate that. (Works fine on Firefox for Android, have no Macs to test) |
That is surprising indeed. I can take a look on mac. |
Temporary fix: #60382 |
…llaumeGomez Revert "Update Source Code Pro fonts to version 2.030" Temporary fix for rust-lang#60365 rust-lang#60146 updated all fonts (not just the fonts that were buggy), however it looks like the new Source Code Pro is buggy. We should test this out of tree: `cargo doc` on anything, replace the font in `target/doc`, and use `python -m SimpleHTTPServer` to see what's going on. Till we figure that out, I'll just back this out. r? @GuillaumeGomez This reverts commit 6bafc58.
…llaumeGomez Revert "Update Source Code Pro fonts to version 2.030" Temporary fix for rust-lang#60365 rust-lang#60146 updated all fonts (not just the fonts that were buggy), however it looks like the new Source Code Pro is buggy. We should test this out of tree: `cargo doc` on anything, replace the font in `target/doc`, and use `python -m SimpleHTTPServer` to see what's going on. Till we figure that out, I'll just back this out. r? @GuillaumeGomez This reverts commit 6bafc58.
…llaumeGomez Revert "Update Source Code Pro fonts to version 2.030" Temporary fix for rust-lang#60365 rust-lang#60146 updated all fonts (not just the fonts that were buggy), however it looks like the new Source Code Pro is buggy. We should test this out of tree: `cargo doc` on anything, replace the font in `target/doc`, and use `python -m SimpleHTTPServer` to see what's going on. Till we figure that out, I'll just back this out. r? @GuillaumeGomez This reverts commit 6bafc58.
…llaumeGomez Revert "Update Source Code Pro fonts to version 2.030" Temporary fix for rust-lang#60365 rust-lang#60146 updated all fonts (not just the fonts that were buggy), however it looks like the new Source Code Pro is buggy. We should test this out of tree: `cargo doc` on anything, replace the font in `target/doc`, and use `python -m SimpleHTTPServer` to see what's going on. Till we figure that out, I'll just back this out. r? @GuillaumeGomez This reverts commit 6bafc58.
This seems to be fixed now (thanks!). This is a known bug in Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1520157 Is it worth keeping this issue open? The newer versions of Source Code Pro have a few newer glyphs and updates, but I don't know if there are any improvements that are important at this time. For details, the version used in rustdoc is 1.017 which has 965 glyphs. The latest version of 2.030 has 1585 glyphs. Google fonts serves 1.017. Adobe's typekit serves 2.010, but with a very small subset of glyphs (393). I would be inclined to just close this for now. The only alternative I can think of is someone could rebuild the fonts from source, removing the colored/svg glyphs to avoid the firefox issue. Or could wait for it to be fixed in Firefox, but I'm not sure what rustdoc's browser compatibility rules are. |
On the recently nightlies, I've noticed that all <code> and <pre> text is being rendered with all black text on Firefox (66.0.3) on macOS only. This is particularly difficult to read with the dark theme.
I bisected the change to #60146 (first starting with nightly-2019-04-24). cc @Manishearth
Other browsers and OSs don't seem to be affected. I tried with a brand new firefox profile, and I also tested on multiple macs, all with the same results. Turning off "Source Code Pro" in the CSS inspector fixes the color.
This seems very peculiar, so I was wondering if anyone else can reproduce it.
The text was updated successfully, but these errors were encountered: