A performance minded developer may prefer to have a faster initial experience that uses a fallback font, and only leverage the nicer web font on subsequent visits after it has had a chance to download. To make matters worse, developers have limited control in deciding how these rules will affect their application. Safari has no timeout behavior (or at least nothing beyond a baseline network timeout).If the requested font is not yet available, a fallback is used, and text is re-rendered later once the requested font becomes available. Internet Explorer has a zero second timeout which results in immediate text rendering.If the font manages to download, then eventually a swap occurs and the text is re-rendered with the intended font. Chrome and Firefox have a three second timeout after which the text is shown with the fallback font.
0 Comments
Leave a Reply. |