fonts.com javascript not working in safari or chrome

Steiner (2020) introduces a work-around that is currently (as of January 2021) in active development: Local Font Access API.

Which is why I’ve decided to write down this article. Surprisingly, the lack of support for self-hosted fonts by the latest versions of Safari is rarely mentioned in any article that I've seen advocates the self-hosting of Google Fonts for the best performance. If the glyphs do not match, the attacker knows that a default replacement font was used since the corporate font was not installed. If the glyphs match the known shape of the corporate font, the attacker has a hit. The attacker would attempt rendering text set in these fonts on a canvas and measure the glyphs. … An attacker can try to determine what company someone works for by testing for the existence of a large number of known corporate fonts like Google Sans. For example, Google has a corporate font called Google Sans. A lot of companies have their own corporate fonts that are installed on employees' laptops. … the list of fonts a user has installed can be pretty identifying.

Steiner (2020) explains what it is, in a very approachable way: Searching over Twitter, I found several tweets reporting the same problem.Īnd the reason is to prevent browser fingerprinting. Still, it’s weird why only Safari fails to render self-hosted Google Fonts. I should have at least specified sans-serif as a fallback for the font-family CSS property. Times New Roman, the default font of the web since Day 1. Poppins, a geometric sans serif font from Google Fonts to go well with the geometric design of my website, is beautifully rendered.

With Chrome (and Edge, Firefox, and Opera), it looked like: woff2 files (with the help of Google Webfonts Helper) to reduce the file size, and uploaded them by pushing with Git LFS to my GitHub repo, and deployed the site with Netlify.

ttf files from Google Fonts, converted them into. So I wrote up the declaration myself, downloaded the. With my little web app ( Triangulum Color Picker-an original color picker), I tried self-hosting Google Fonts, after being convinced that there is now no performance gain in any situation by using the Google Fonts server ( Wicki 2020 see also Pollard 2020). The root cause is unclear, though.Īpparently it’s best NOT to self-host Google Fonts, because the latest versions of Safari will fail to render them. The issue with Safari discussed below gets fixed when I deploy another Next.js site (static generation) with Cloudflare Page rather than with Netlify.

Fonts.com javascript not working in safari or chrome