3 ms·
Showing nothing for 3 seconds beats just using the fallback and switching when the download finishes? It's great you collected data, but I think the working hy
by revelation 13y ago
Showing nothing for 3 seconds beats just using the fallback and switching when the download finishes?
It's great you collected data, but I think the working hypothesis is flawed.
- Kequc 13y agoI would rather not have the fallback font as the font changing suddenly is jarring. It also can muck up spacing to quite a high degree. If for example you were at an anchor quite a distance down the page and then the entire page shifts. I added a Feedback drawer to the top of my site. Javascript would determine the height of the drawer then set the top position equal to the inverse of it's height. That way the drawer was completely hidden. However when a font was loaded the height of the drawer changes and then you've got it sticking down over of the top of the page. These kinds of things are really frustrating. I'd like to see the page not display until the fonts are loaded and I'd like to see Chrome start shipping with some of the more common web fonts included.
- pkartistry 13y agoIn some instances, showing nothing for a few seconds can be preferable. Some fonts are very different in size and that web font could flow a lot differently than what the fallback is. If you start reading and the font changes halfway through the sentence, it can be very jarring and slow you down as you try to find your place again. A lot of the problem is poorly implemented web fonts that are not optimized, or web designers going crazy and including 6-8 different font/weight combinations. Having half a meg of web fonts download is no different than using way too many images that are not compressed enough.