website render issue on Windows 7 + Chrome 78*

[neolit123]

What happened:
hello, i was trying to read the release notes for the latest release on the website:
https://coredns.io/2020/06/15/coredns-1.7.0-release/
the page is not rendering correctly for me on Chrome.

---

screenshot1

---

screenshot2

---

What you expected to happen:
the page renders correctly.

How to reproduce it (as minimally and precisely as possible):
a colleague of mine said that they don't have the same issue.
(possibly a newer version of Chrome + Windows 10)

Anything else we need to know?:

• renders fine under Firefox.

if i "inspect" the page under Chrome and remove the usage of the "Lato" font the page renders correctly:

Environment:

• Windows 7 64bit
• Chrome 78.0.4050.0

[miekg]

shouldn't a browser use another font if the first one is unavailable?

[neolit123]

AFAIK (not a web developer though), it if Lato is not installed on the system it should fallback to the second entry in the list, although that does not seem to happen.

C:\Windows\Fonts>dir Lato*
...
 Directory of C:\Windows\Fonts

File Not Found

[miekg]

[ Quoting <notifications@github.com> in "Re: [coredns/coredns.io] website re..." ]

AFAIK (not a web developer though), it if Lato is not installed on the system it should fallback to the second entry in the list, although that does not seem to happen.

yes, that mimics what I undertand here; hence the super generic fallback. I don't have windows (and certainly not windows 7), so I can't check

[neolit123]

i just tried on a Windows 10 machine that doesn't have Lato in \Windows\Fonts and it seems to work fine.

if i modify font-family: Lato, sans-serif to be e.g. font-family: Foo, sans-serif the fallback works, which tells me that "Lato" might be installed somehow, but not rendering properly. or maybe this version of Chrome thinks it's installed.

i know Slack uses Lato, but it does not install the font and just has it in it's resource folder.

i'm going to close this ticket given this works on my other Windows machine. this might be a weird bug with the Chrome / Windows 7 combination.

thanks!