From 8744ad955a30b82f7bf9ceda3f58da9f09e8c86c Mon Sep 17 00:00:00 2001 From: Alex Ivanovs Date: Sat, 8 Jul 2023 15:18:23 +0200 Subject: [PATCH] Fix a broken link (expired domain) Fixing a link. --- src/site/content/en/blog/webfonts-quick/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/site/content/en/blog/webfonts-quick/index.md b/src/site/content/en/blog/webfonts-quick/index.md index 7e9097c13b5..33e7c0713c0 100644 --- a/src/site/content/en/blog/webfonts-quick/index.md +++ b/src/site/content/en/blog/webfonts-quick/index.md @@ -129,7 +129,7 @@ Inducing a headache yet? If you'd rather just get this off the ground quickly, h ### Mobile support? -Mobile Safari [supports](http://mwhenry.com/blog/2009/12/font-face-support-table/) SVG webfonts as of iOS 3.1 and Android supports otf/ttf as of version 2.2. But should your mobile users get this enhanced typographic experience? I'd recommend no. The predominant reason is due to how WebKit handles text that is awaiting a custom font via @font-face: the text is invisible. So on a low-bandwidth mobile connection, your users will see no text at all until the ~50k of font data has loaded. The Webkit team is pursuing a solution of turning on a fallback font after a few seconds have expired, but until that has landed, I wouldn't consider it fair to subject your users to such roadblocks between them and your content. +Mobile Safari [supports](https://web.archive.org/web/20100203095842/http://mwhenry.com/blog/2009/12/font-face-support-table/) SVG webfonts as of iOS 3.1 and Android supports otf/ttf as of version 2.2. But should your mobile users get this enhanced typographic experience? I'd recommend no. The predominant reason is due to how WebKit handles text that is awaiting a custom font via @font-face: the text is invisible. So on a low-bandwidth mobile connection, your users will see no text at all until the ~50k of font data has loaded. The Webkit team is pursuing a solution of turning on a fallback font after a few seconds have expired, but until that has landed, I wouldn't consider it fair to subject your users to such roadblocks between them and your content. ## Webfont services A number of services wrap the @font-face feature in an easy API, oftentimes letting you add a single CSS or script line to your HTML and some configuration and you're all done. Many like [WebInk](http://www.extensis.com/en/WebINK/), [Typekit](http://typekit.com/), and [Fontslive](http://www.fontslive.com/) will allow you to use the fonts (sometimes up to a bandwidth cap) for a monthly fee. Using these services is very convenient for the casual developer, handing off some of the complications of serving a cross-browser solution