-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Troubleshoot fonts #154
Comments
At first look, I assumed this was because in our umbrella-citylimits/wp-content/themes/citylimits/less/_variables.less Lines 20 to 21 in b029d63
However, here's Adobe's usage instructions for
|
What's even more strange is that they're complaining about it working on some pages, but not others. All places that use that font are using the same @benlk any ideas on this? |
@MirandaEcho Could you attach the screenshots he sent over? |
His screenshots were posted in this spreadsheet, but there's no way to grab them from there. There's also some more info from him, its in row 44: https://docs.google.com/spreadsheets/d/1Wsk4aClpbsxoiTSgm2yGQOY-6T9r_MrhZ-nT9msFnys/edit#gid=0 Let me know if I need to grab additional info from him, but I was able to see the issue in my own browser as well - in most places the correct fonts are not rendering. On article pages, the headline is correct, but seemingly nowhere else, including the homepage: |
Okay, so, this isn't an issue then with the |
"The new fonts are inconconsistently rendering on some browers and some pages. HTML allows you to program backup fonts, so the "Neue Haas Groetsk Text" appears to be default, but if browers can't find it it renders Helvetica. For me, on Safari and Adina on Chrome, it looks like the site is showing Helvetica for Headlines on the homepage and only showign the new ""Neue Haas Groetsk Text" font on article pages. Its hard to check and know for other elements but likey happening with more than headlines. Many of the fonts just look like Helvetica to me. Above image is homepage. below image is article page"
At one point, @joshdarby and I discussed this and determined its a CSS fix we need to implement on our end.
This is non-billable and needs to be logged directly in the covered support project in Everhour
The text was updated successfully, but these errors were encountered: